Adobe Analytics
Adobe Analytics is a cloud computing and enterprise analytics system that helps you uncover business opportunities and successes by turning customer interactions into actionable insights. Send user behavior data, custom events, and general tracking variables to Adobe based on a user's actions in your app with the Swrve Adobe Analytics integration.
Supported actions​
Swrve's Adobe Analytics integration supports the following outbound actions:
- Submit page view (user) interactions to enhance the user behavior data
- Track user product views, cart events, checkouts, and purchases
- Submit generic tracking data about the user
- Clear tracking variables for unique users
There are two main steps involved in configuring the actions for the Adobe Analytics integration:
- Create a custom event in the Swrve SDK for the user action you want to use to trigger the selected outbound action; for example, add_to_cart.*
- Create a rule that is triggered on receipt of the designated event and uses the outbound action to send events or user profile information to Adobe Analytics.
Use cases​
Track generic data​
Submit generic tracking data or events logged by the user to Adobe Analytics. This could be Swrve events or any custom data you want to track in Adobe Analytics.
Track page views​
Submit page view events when a user navigates to different pages within your app.
Track commerce events​
Track purchase flow events from product view to purchase in Adobe Analytics.
Clear tracking variables​
Reset the all the tracking variables for a user in Adobe Analytics when they take a specific action in your app.
Adobe Analytics configuration​
In most instances, your CSM will set up your Adobe Analytics configuration, however you might need to provide them with certain credentials. To view your active Swrve integrations, on the Manage menu, select Adaptors.
- To access the configuration settings, on the Adobe Analytics card, select Configure.
- Complete the following fields as required:
| Field | Description |
|---|---|
| Report Suite | Specifies the report suite where you want to submit data. |
| Data Center URL | The data center where your report suite resides. Adobe ClientCare can provide the domain name of the Adobe data collection servers to which you should send data. |
Carefully check your configuration parameters. The Adobe Analytics API does not allow us to detect invalid parameters. All tracking calls with invalid parameters may be lost without providing any error messages. 3. To save the configuration settings, select Save.
Once saved, the configuration status changes to Active and the Deactivate button is available. If you Activate or Deactivate the integration at any time, the changes apply to any outbound actions you have configured.
Adobe Analytics actions​
This section describes the fields that are included when creating a new rule using the selected action. Most fields have the option to manually enter the value or to select a user property or event payload from the list to have Swrve automatically populate the value when the rule is processed.
Generic Tracking Call​
Submit generic tracking data or events to Adobe Analytics.
| Field | Description |
|---|---|
| Visitor ID | The custom unique value that you use to identify users on your site. Custom visitor IDs can include alphanumeric characters up to 100 characters. Avoid using dashes, spaces, underscores, or symbols in the value. |
| Page URL | The URL of a given page. Either Page name or Page URL is required. |
| Page Name | The name of a given page. Either Page name or Page URL is required. |
| Timestamp | The date and time of the page hit. To submit time-stamped events, Adobe Client Care must enable timestamp support on the report suite. |
| Server | The hostname of your site. |
| IP Address | The IP address of the user's device. |
| User Agent | The user's browser type and operating system (OS). |
| Traffic Variables | The variables (props) you want to use for building custom reports within the Analytics Traffic Module. Props might be used as counters (to count the number of times a page view is sent), for pathing reports, or in correlation reports. |
| Conversion Variables | The variables (eVar) you want to use for building custom reports within the Analytics Conversion Module. When an eVar is set to a value for a visitor, Analytics remembers the value until it expires. Any success events that a visitor encounters while the eVar value is active are counted toward the eVar value. Events - records common shopping cart success events and custom success events. Campaign - identifies marketing campaigns used to bring visitors to your site. The value of the campaign is usually taken from a query string parameter. |
| Context Data Variables | Context Data allows you to define the name of the variable that you assign a particular value to, without advance knowledge of the types of variables Analytics offers. These values will then be available in the Processing Rules interface for assignment to particular variables (props, eVars, or events). Valid context data variables contain only alpha-numeric characters, underscores, and periods. Adobe does not guarantee data collection in processing rules if you include other characters, such as hyphens. These variables may be name-spaced; for example, my.age uses a namespace of my. Do not start context variables with a., as Adobe reserves use of the a. prefix. |
Page View Track​
Submit user interaction data to Adobe Analytics.
| Field | Description |
|---|---|
| Visitor ID | The custom unique value that you use to identify users on your site. Custom visitor IDs can include alphanumeric characters up to 100 characters. Avoid using dashes, spaces, underscores, or symbols in the value. |
| Page URL | The URL of a given page. Either Page name or Page URL is required. |
| Page Name | The name of a given page. Either Page name or Page URL is required. |
| Timestamp | The date and time of the page view. To submit time-stamped events, Adobe Client Care must enable timestamp support on the report suite. |
| IP Address | The IP address of the user's device. |
| Additional Parameters | Add any additional Analytics parameters you want to use for reporting. |
| Context Data Variables | Context Data allows you to define the name of the variable that you assign a particular value to, without advance knowledge of the types of variables Analytics offers. These values will then be available in the Processing Rules interface for assignment to particular variables (props, eVars, or events). For naming conventions, see Generic Tracking Call above. |
Track Commerce or Custom Event​
Track product views, cart events, checkouts, and purchases in Adobe Analytics.
| Field | Description |
|---|---|
| Visitor ID | The custom unique value that you use to identify users on your site. Custom visitor IDs can include alphanumeric characters up to 100 characters. Avoid using dashes, spaces, underscores, or symbols in the value. |
| Events | Adobe events variable. Separate event names by comma. Use custom event names or use the following predefined events: prodView, scView, scOpen, scAdd, scRemove, scCheckout, purchase. |
| Page URL | The URL of a given page. Either Page name or Page URL is required. |
| Page Name | The name of a given page. Either Page name or Page URL is required. |
| Timestamp | The date and time of the event. To submit time-stamped events, Adobe Client Care must enable timestamp support on the report suite. |
| Server | The hostname of your site. |
| IP Address | The IP address of the user's device. |
| Conversion Variables | The variables (eVar) you want to use for building custom reports within the Analytics Conversion Module. When an eVar is set to a value for a visitor, Analytics remembers the value until it expires. Any success events that a visitor encounters while the eVar value is active are counted toward the eVar value. Events - records common shopping cart success events and custom success events. Campaign - identifies marketing campaigns used to bring visitors to your site. The value of the campaign is usually taken from a query string parameter. |
| Additional Parameters | Add any additional Analytics parameters you want to use for reporting. |
| Context Data Variables | Context Data allows you to define the name of the variable that you assign a particular value to, without advance knowledge of the types of variables Analytics offers. These values will then be available in the Processing Rules interface for assignment to particular variables (props, eVars, or events). For naming conventions, see Generic Tracking Call above. |
Clear Tracking Variables​
Clears the following tracking variables for the user: props, eVars, hier, list, events, eventList, products, productsList, channel, purchaseID, transactionID, state, zip, campaign.
| Field | Description |
|---|---|
| Visitor ID | The custom unique value that you use to identify users on your site. Custom visitor IDs can include alphanumeric characters up to 100 characters. Avoid using dashes, spaces, underscores, or symbols in the value. |
| Page URL | The URL of a given page. Either Page name or Page URL is required. |
| Page Name | The name of a given page. Either Page name or Page URL is required. |