![]() You also don't need to fire the Identify function each time. So if you add the identity into the tracker with the Identify function before the tracking code loads, it will then call the trackPageView function, passing the identity to HubSpot, which will associate the analytics with the contact record. ![]() Since the Identify function only sets the identity in the tracker, that identity still needs to be passed to HubSpot in order to associate the analytics to the correct contact record. I'd suggest that, but it just needs to fire before making a separate trackPageView or trackEvent call. It's not so much that the Identify function needs to fire prior to the tracking code. Let me know if you have any questions about how this works. But this should enable you to track analytics from your CMS in HubSpot, without your users submitting a HubSpot form. The data is only passed to HubSpot when the trackPageView or trackEvent functions are called. Just make sure to take a look at the note in that article. The analytics from the usertoken will be associated to the email address that you provide, which it sounds like you have access to through your CMS, after your users sign up. You can then use the Identify function, documented here. The tracking code associates that cookie to a usertoken. Once the tracking code is installed, it will set the hubspotutk cookie in the visitor's browser, which will track actions like page views. If you haven't done that yet, we have some documentation on it here. You'll want to make sure that these pages have the HubSpot tracking code on them. ![]() Hi sounds like you're on the right track here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |