What to expect
This integration will allow you to analyze data from anywhere in the customer journey using your Adobe Analytics segments. Contentsquare allows you to use your Adobe Analytics segments in every Contentsquare feature (Journey Analysis, Page Comparator, Zoning Analysis, Session Replay).
You must to add a snippet of code to your mobile application code to be able to import your segments. This code will push a unique identifier to Adobe Analytics and to Contentsquare.
It allows us to match Adobe Analytics sessions with Contentsquare ones.
What we collect
Refers to the unique value used to cross-reference Adobe segments with Contentsquare sessions.
Step 1: Create Profile and API project
Follow the instructions in the 'Create an Adobe Analytics Profile' and 'Create an API Project sections' in this Adobe Analytics - Connector document.
- Adobe Analytics connector allows you to import your Adobe Analytics segments into Contentsquare and use them to filter Contentsquare analytics.
Step 2: Configure a dedicated Contentsquare eVar
1. Click 'Analytics' > 'Admin' > 'Report Suites'
2. Select your Report Suite
3. Click 'Edit Settings' > 'Conversion' > 'Conversion Variables'
4. Click 'Add New'
5. Fill the fields with the following parameters set the way you see below:
6. Click 'Save'
Step 3: Create ContextData
1. Go to 'Adobe Experience Platform Data Collection'
2. Click 'Data Elements' > 'Add Data Element'
3. Fill with/select the following:
- Data Element Type:
- Context Key:
Here is what your final result should look like:
4. Click 'Save'
Step 4: Create processing rule
The goal of the processing rule we will create is to forward the received Context Data into the eVar.
Processing rules are set on report suites (screenshot for complete setup is available after the steps)
1. Click Analytics > Admin > Report Suites
2. Select your Report Suite.
3. Click 'Edit Settings' > 'General' > 'Processing Rules'
4. On the Processing Rules page, click 'Add Rule'
5. Choose a Rule Title, for instance
csMatchingKey Context Data to eVar
6. In Always Execute, choose from dropdown lists:
Overwrite value of
csMatchingkey (eVar1): this is the eVar previously created
csMatchMatchingKey(Context Data): this is the Context Data previously created
7. Click 'Add Action' and then set
csMatchingkey (Context Data)
8. Add a note containing details about the rule, for example:
SDK Context Data mapping to eVar for Contentsquare
9. The processing rule has the following parameters set the way you see below:
10. Click 'Save'
Step 5: Set up Adobe Analytics connector
Setup the Adobe Analytics Connector from your Contentsquare project using this document: Set up your Adobe Analytics Connector
Step 6: Code snippet to implement in your application
- iOS code implementation
- Android code implementation
- Flutter code implementation
- React Native code implementation
This integration relies on pushing an identifier (the 'csMatchingKey') in an Adobe eVar. This identifier is then used to match our sessions and flag them as belonging to the queries' Adobe segments.
Adobe limitation: when a variable reaches 500,000 unique values, data is bucketed under "Low Traffic", meaning that identifiers falling in that bucket cannot be accessed to match Contentsquare sessions. This mechanism results in a form of random sampling on the Adobe side past the 500,000 thresholds, and this sampling gets more aggressive after 1,000,000 unique values. This can create data gaps between the number of sessions observed in Adobe vs Contentsquare for a given segment.
You can change the limit threshold by contacting Adobe, as suggested by Adobe in their documentation.
See Adobe Analytics FAQ.