📘 This article provides the steps to integrate Adobe Analytics (Legacy) with Botify. Refer to Integrating with Adobe Analytics 2.0 for information on the latest integration.

Overview

To see visits from Adobe Analytics in your Botify analyses, you must leverage the Adobe Analytics capability that exports a data feed to an external storage bucket. For Botify to access this data, you will need to send this data feed to a dedicated AWS S3 storage bucket, provided by Botify. Since the Botify integration uses this method, you must have the Analytics Data Feeds module activated in your Adobe Analytics account.

Adobe Analytics Full Dataset

Access the full Adobe Analytics dataset here. The Botify integration requires you to export a subset of the full dataset, referred to as the “Minimum Dataset” in this article.

Adobe Analytics Minimum Dataset

To access the minimum dataset for the integration:

Select a Report Suite, or create one if you do not have one.
1. Identify the report suite that contains the Adobe Analytics Data to integrate into Botify. If you do not have a report suite yet for the site you want to monitor, work with your analytics team to create one.
2. Provide the ID of the Report Suite to Botify, along with the link to the Botify project(s) you want the Adobe analytics data to be integrated into. To find it: https://webanalyticsfordevelopers.com/2013/05/14/finding-a-report-suite-id/
3. In return, Botify will provide you with:
  1. Access Key ID
  2. Secret Access Key
  3. Bucket region: us-east-1
  4. Bucket name: com.botify.saas.production.adobe
  5. Bucket folder
Create a Data Feed
We need you to send the data feed to a specific AWS S3 bucket with the subset of information you will provide us by following the Adobe Analytics documentation to create a data feed. To configure the export from Adobe Analytics, start creating a new feed and fill in the requested information as follows:
1. Feed Information:
  1. Report Suite: Select the report suite.
  2. Email when complete: optional.
  3. Feed Interval: Hourly.
  4. Delay Processing: No Delay.
  5. Start & End Dates: Continuous Feed.
2. Feed Destination:
  1. Destination Type: S3.
  2. Bucket: Enter bucket name as provided by Botify (syntax: com.botify.saas.production.adobe).
  3. Path: Enter bucket folder as provided by Botify (syntax: customer._/<project_slug>/).
  4. Append Report Suite ID to Path: Unchecked.
  5. Access Key: Enter access key as provided by Botify.
  6. Secret Key: Enter secret key as provided by Botify.
3. Data Column Definitions Options:
  1. Remove Escaped Characters: No.
  2. Include Data Manifest: Yes.
  3. Compression Format: GZIP.
  4. Packaging Type: select the “Multiple Files” option.
4. Data Column Definitions Content to be included:
  1. exclude_hit
  2. hit_source
  3. post_visid_high
  4. post_visid_low
  5. post_page_event
  6. visit_num
  7. visit_start_time_gmt
  8. visit_page_num
  9. page_url
  10. post_cust_hit_time_gmt
  11. visit_ref_domain
  12. visit_ref_type
  13. visit_search_engine
  14. user_agent
  15. paid_search
5. Expected result: The following three files per hour in the bucket:
  1. <report_suite_id>_YYYYMMDD-HHMMSS.txt: Manifest file that includes a reference to the lookup data and the delivery contents files.
  2. <reportsuite_id>--lookup_data.<compression_suffix>: Lookup file without hit_data.tsv inside (zip or tar.gz).
  3. -<reportsuite_id>-.tsv.<compression_suffix>: A delivery content file archive that contains a single hit_data.tsv with approximately 2 GB of uncompressed data (zip or gz).
Let's test it!
As soon as you have the first version of the export with at least three days of data, inform Botify Support, and we will test the Adobe Analytics integration and validate the dataset.

For more details, refer to: https://marketing.adobe.com/resources/help/en_US/reference/datafeeds_contents.html

Field Descriptions

Column name	Column description
exclude_hit	Hit excluded by client rule.
hit_source	A flag for the back-end processing to know what type of hit the data is.
post_visid_high	The visid_high value that we ended up using for the hit.
post_visid_low	The visid_low value that we ended up using for the hit.
post_page_event	Page event ID, the type of hit that is sent in the request.
visit_num	The number of the current visit (Incremented each time a visitor returns to the site)
visit_start_time_gmt	The GMT timestamp of the first pageview in this visit.
visit_page_num	The page sequence number in the current visit.
page_url	The start page for the visit.
post_cust_hit_time_gmt	Timestamp actually used for the hit, this is cust_hit_time_gmt for timestamp-enabled report suites, or hit_time_gmt otherwise.
visit_ref_domain	The referring domain of the visit (based on referrer).
visit_ref_type	An integer representing the type of referral for the visit. Lookup values can be obtained from referrer_type.csv lookup table.
visit_search_engine	The search engine used to find the site.
user_agent	User-agent as found in the HTTP header sent from the browser.
paid_search	A (1/0) flag that determines if the hit was used for paid search tracking.

Contact Support

If you need any assistance with setting up the Adobe Analytics integration, please contact Support using the email address for your region:

North America: support-americas@botify.com
EMEA: support-emea@botify.com
Asia: support-asia@botify.com