Web Analytics Integrations + New Segment ID Only Option
You may have recently heard about the new update to the 6sense APIs here, but are you wondering how this will impact your Web Analytics Integrations to Google Analytics & Adobe Analytics? Below, I'll explain the impact and how you can update your integration to only use Segment ID!
Additionally, given you only want Segment ID in the API, you will need to update your API Settings. The Segments screens have now been updated to include easy access to the Segment ID. More info on that here.
We recommend specifically publishing Segments to the API as well, so be sure to identify the Segments you want to sync first and then Publish them using the Settings interface.
If this is the first time you're hearing about the integration, all you need to do is make sure you have upgraded to WebTag 2.0 and then just follow the WebTag 2.0 Guide: Install the Company Identification API on Google Tag Manager & GA4.
If you already have a Google Analytics integration in place, it was likely set up for Universal Analytics (GA3). Now that Google has deprecated GA3, you will need to reconfigure the way you are syncing 6sense Segments to Google Analytics Audiences so they are compatible with GA4. Starting from scratch is recommended. This will involve completely removing the existing 6sense WebTag, and configuration in GTM such as event tags and variables. Then you can follow the above guide.
Now, if you have Audiences set up to sync 6sense Segments to GA360 or AdWords, once you have the set-up completed per the link above, you will just need to update the definition of the Audience. Here are some details on how to set up an Audience in GA4.
Adobe Data Collection (Adobe Launch)
If this is the first time you're hearing about the integration, we recommend you have upgraded to WebTag 2.0 and then just follow the WebTag 2.0 Guide: Install the Company Identification API on Adobe Launch (Data Collection). WebTag 2.0 provides the popular "Limit API Calls" feature, which is not available in the Adobe Extension at this time.
With WebTag 2.0
To use Segment IDs instead of Names, just configure an eVar to contain the Segment IDs. The example code shows "eVar132" set to hold the Segment IDs.
Then in 6sense, retrieve the Segment IDs for your desired segments from the platform and set up rules in Adobe Analytics to identify your Web Traffic based on this eVar.
You may also work with your Adobe team to configure this custom code to your website's requirements as they may be different than the example code provided.
With the Adobe Extension
If you already have the Adobe Extension installed, there will be an upgrade available. Upgrade the extension and you will have some new options available.
In the Extension settings, you will need to place your Segments API Token. If you do not have one, please submit a Support Case requesting a token for your Adobe Extension integration.
In the API Mapping Rule, you will see that Segment Names are replaced with Segment IDs. Retrieve your Segment ID from the 6sense platform and paste it into the Adobe UI.
And with all that, you should be all set!
For any questions or concerns, please reach out to 6sense Support.