Adobe Analytics

Kameleoon’s native bridge with Adobe Analytics allows marketers to analyze any Kameleoon campaigns performance directly into Adobe Analytics dashboards by storing the data in an Adobe Analytics eVar. Key benefits:

• Leverage all your existing Adobe Analytics reports to view how your visitors exposed to a campaign (A/B test or Personalization) behaved on your site.
• Spot new opportunities using Adobe Analytics reports.

​

Activate Adobe Analytics on Kameleoon

​

Integrations page

To install and enable Adobe Analytics on Kameleoon:

1. Open the Kameleoon app.
2. Click Admin > Integrations.
3. Search for the Adobe Analytics integration and click it.
4. Click Install.
5. Select the project on which you want to activate Adobe Analytics.
6. Click Next.

7. Configure the integration:
   • Adobe Analytics object: The s_objectID variable. See Adobe’s documentation
   • Forbidden variables eVars: Select the eVars you want to block Kameleoon from sending events to. See Adobe’s documentation
   • Default variable: Choose the default variable to send data to Adobe Analytics.
8. Click Next.

You also have to create a conversion variable in Adobe Analytics. The Adobe Analytics variable (Omniture object) is s by default, but you should verify this information with your IT team. Once you have configured the tool, click Validate. You will see it appear in the installed tab with the number of projects on which you’ve configured the tool. Kameleoon transmits your experiment results to Adobe Analytics if you’ve installed the tool’s script on your pages.

​

Conversion variable

It’s necessary to create a conversion variable, also called eVar, which Kameleoon uses to transfer your experiment data to Adobe Analytics. To do so, log into your Adobe Analytics. You must create a new conversion variable:

1. In Adobe Analytics, click Admin > Report Suites.
2. Select a report suite.
3. Click Parameters > Conversion > Conversion variables.
4. Click Add new.
5. Fill in the required fields.
6. Click Save.

​

Associate Adobe Analytics with an experiment

Once you complete these steps, you can use Adobe Analytics as a reporting tool.

​

In the Graphic/Code editor

To associate Adobe Analytics with an experiment in the Graphic or Code editor:

1. Click Finalize
2. Select Adobe Analytics in the Integrations section.
3. Enter the eVar that you created in the Custom variable (eVar) field.

Kameleoon pushes your experiment’s results into the Adobe Analytics solution.

​

On a feature flag

To add Adobe Analytics to a feature flag:

1. Click Edit on the feature flag you want to track.
2. Click Integrations in the Reporting section. All the integrations you’ve enabled appear.
3. Toggle Adobe Analytics on for Delivery rules, Feature experiments, or both.

Learn how to manage third-party analytics integrations

​

How Kameleoon tracks experiments in Adobe Analytics

Kameleoon’s native Adobe Analytics integration sends experiment exposure data to Adobe Analytics automatically, using the configured eVars. Depending on when an experiment triggers relative to Adobe’s pageview tracking, Kameleoon either includes the experiment data in the existing Adobe pageview or sends an additional tracking call.

​

Default tracking behavior

By default, Kameleoon can send a dedicated Adobe Analytics tracking call (s.tl()) when Kameleoon exposes a visitor to an experiment. Kameleoon doesn’t send an additional call every time it executes. Tracking calls remain subject to Kameleoon’s exposure tracking and deduplication mechanisms. The additional s.tl() call is a custom link tracking hit, not a pageview, so the call doesn’t increment the Adobe Analytics pageview count. In the default configuration, Kameleoon doesn’t need the s.tracksent variable to determine whether it can send an additional tracking call.

​

Reducing additional Adobe Analytics calls using s.tracksent

To minimize the number of Adobe Analytics calls, Kameleoon supports an optional configuration that uses the s.tracksent variable to determine whether the browser has already sent the initial Adobe pageview. When you enable the option, the integration follows this logic:

• s.tracksent is false: The browser hasn’t sent the Adobe pageview yet. Kameleoon prepares the experiment eVars so that the upcoming Adobe pageview (s.t()) includes them, which avoids a separate tracking call.
• s.tracksent is true: The browser has already sent the Adobe pageview. Kameleoon can trigger an additional s.tl() call to record newly triggered experiment exposures.

Additional calls remain subject to the integration’s normal tracking and deduplication checks.

​

Configure s.tracksent

Your Adobe Analytics implementation must manage the s.tracksent variable. Adobe Analytics doesn’t update the variable automatically, because it isn’t a native Adobe Analytics variable. To configure the variable:

1. Initialize s.tracksent = false before you send the first Adobe Analytics pageview.
2. Send your normal Adobe pageview with s.t().
3. Set s.tracksent = true immediately after you dispatch the pageview call.

With the variable in place, Kameleoon distinguishes experiments that trigger before the initial pageview from experiments that trigger afterward. If your website is a single-page app (SPA) with virtual pageviews, manage the variable consistently with your pageview tracking lifecycle.

​

What happens if s.tracksent isn’t defined

If the page doesn’t define s.tracksent, the behavior depends on the integration configuration:

• Default configuration: Kameleoon can send an additional s.tl() tracking call without relying on s.tracksent.
• Optional tracksent-based configuration: Kameleoon can’t determine the pageview status from the variable alone. Whether Kameleoon triggers an additional call depends on the available tracking state and the integration’s tracking conditions.

For predictable behavior, explicitly initialize and maintain s.tracksent when you use the optional configuration.

​

Recommendation

If your priority is to reduce the number of Adobe Analytics tracking calls, Kameleoon recommends enabling the tracksent-based configuration and making sure the variable accurately reflects whether the browser has sent the initial Adobe pageview. With that setup, Kameleoon reuses the existing Adobe pageview whenever possible while still tracking exposures that occur after the pageview.