SalesForce and Adobe Analytics Integration

Following can be expectation from:

  1. Want two way integration between Adobe Analytics and SFDC
  2. Ready made connector is not available under Data Connector so custom solution has to be designed for that.

There are  couple of ways by which data can be sent from Adobe Analytics to SFDC.

  1. Data warehouse API to send data in SFDC
  2. Reporting API to send data to SFDC
  3. Data Extract report and inject that into SFDC
  4. Data Warehouse report and inject that into SFDC
  5. Data feeds: Receive an hourly or daily export of raw data. Every row is an individual hit, and every column is a variable. Data feeds are typically sent to FTP sites. Inject the file into SFDC

There are  couple of ways by which data can be sent from SFDC to Adobe Analytics.

  1. Use Data Source API
  2. Use Data Source FTP

Before opting the solution do POC in terms of dimension and metric which need to be imported and exported. That will help to decide that which method or option is good to go forward.

Segregate Internal & External Traffic In Adobe Analytics

Within the Adobe Analytics tool there are 4 main ways to deal with IP address exclusions:

1) Out of the box “Exclude by IP” functionality

This method can be accessed by going to the global ‘Admin’ drop down menu and selecting “Exclude by IP”.  Instructions on how to use this are contained within the page and it is by far the easiest method of removing traffic from specific IP addresses/ranges.

However, the disadvantage of this is that any excluded data is effectively lost for ever so this is not suitable if you ever want to analyse data from internal traffic for a given report suite.

Hint: what is not immediately obvious is that the exclusions work on a report suite by report suite basis – you need to make sure the correct report suite is selected in the top right hand corner

2) Get Adobe engineering to build a DB VISTA Rule

Typically this method would be used if you wanted to siphon off the internal traffic into a separate report suite to analyse separately from your external traffic.  However, Adobe engineering have an awful lot of flexibility within VISTA rules you are not limited on just siphoning data to a separate report suite if you can think of something more creative that you want to do!

The basic approach would be for Adobe Engineering to build a “DB” (Database) Vista rule that allow you to upload and manage via FTP a list of IP address that are excluded (i.e. allowing you to manage going forward without further intervention from Adobe Engineering).

As with all VISTA rules there will almost certainly be a cost associated with this.

3) Use Processing Rules in combination with Virtual Report Suites

IP address is available in processing rules, even if you’ve set your privacy settings to remove IP a ddress from your data.

This means you can using processing rules to set a value into a variable whenever you see an internal IP address (e.g. overwrite prop1 with a custom value of “internal traffic”)

The value captured can be used to segment your data or, as we do, used to created virtual report suites (e.g. one with external traffic, one with internal traffic)

The advantages of this is that it is non destructive and there is no cost. Though it is not retroactive process and will be affective after the setup.

4) Use segment or VRS

If you have list of IP address available in report suite then you can create segment and apply that on reports or create a VRS and you can share that VRS to stake holders. It is retro-active process.

Impression data to Audience Manager (AAM)

Is Ad Cloud able to pass display media exposure back to AA, and then have this forwarded via Server side ?

Advertising Cloud is able to pass data in Analytics via Adobe server to server integration for Adobe to understand if the ad impacted the consumer to visit the website. For example, Adobe can capture view-through data and understand if someone saw the display ad (delivered via Advertising Cloud) and then went to the advertisers’ web page a few days later (via the Analytics pixel on the web-page), we can capture that as a view-through conversion and say the ad contributed to the person visiting the website. From there, Analytics can understand other ways users are interacting with the web page (bounce rate, page views etc.) to help create audiences to re-target, or build look-a-likes (via pushing Analytics segments into Audience Manager). Additionally, we can create audiences via Analytics data and push those audience segments into Audience Manager through server to server integration to house all segments in one place for organization.

You have the option to push audiences straight from Analytics into Advertising Cloud to target, or can push the audiences into Audience Manager for organization and then push from AAM to Ad Cloud to target.

The benefits of using all three products together are:

– Capture audience and website behavior and use it to build segments of in-market intenders

– Create a single view of the customer form your unified data, enriched and added data

– Deliver a personalized ad to an audience at the right time whenever they are in an authentic and relevant experience

– Continue to personalize through analysis, reporting & optimization

Adobe Analytics Connector with PowerBI

 

With the introduction of new Adobe Analytics connector with PowerBI (Partnership with Microsoft), it becomes very easy to load Adobe Analytics data into PowerBI and perform the analysis.

After launching the connector, it has to be authenticated by Adobe ID.

Complete steps are well explained in the video below:

On web Connect to Adobe Analytics with Power BI

Hope this article was helpful if you have a question then feel free to comment below and share to your friends.

How To Connect Tableau to Adobe Analytics

By default, there is no functionality in Tableau to connect Adobe Analytics or vice versa. Till now there is no Connector available for data transfer developed by Adobe or Tableau.

Option available for now is to get file processed from Data Warehouse which is supported by Tableau i.e

  • Tableau Workbook (.twb)
  • Tableau Packaged Workbook (.twbx)

Update[17-Sep-2020]

We recently came across a new Adobe Analytics Connector for Tableau Software by Daexus- It’s secure, requires no sign-up, and it’s free!

Import your Adobe Analytics data in Tableau in no time.

https://bit.ly/32FXbMi

Another connector by cognetik which is made available to analysts & marketers worldwide.

It’s free to use, for now, it’s got a fairly easy set-up, it takes a few minutes to import the data and it allows for easy refreshes.

In addition to Adobe, works fine with Facebook Ads, Facebook Pages, Adwords, Bing, Kochava, Youtube and Twiter.

Another option is to use reporting API of Adobe analytics, fetch the Analytics data through reporting API and ingest that into Tableau.

How To Connect R-Studio to Adobe Analytics

With the help of Web Services API R-studio can be used to connect Adobe Analytics.

The Web Services APIs provide programmatic access to marketing reports and other Suite services that let you duplicate and augment functionality available through the Analytics interface.

Analytics > Admin > Company Settings > Web Services

RSiteCatalyst is a kind of good package of R.

SCAuth Store Credentials For The Adobe Analytics API

Usage:

SCAuth(key, secret, company = “”, token.file = “”, auth.method = “legacy”, debug.mode = FALSE, endpoint = “”, locale = “en_US”)

Arguments

key
Client id from your app in the Adobe Marketing cloud Dev Center OR if you are using auth.method=’legacy’, then this is the API username (username:company)

secret
Secret from your app in the Adobe Marketing cloud Dev Center OR if you are using auth.method=’legacy’, then this is the API shared secret

company
Your company (only required if using OAUTH2 AUTH method)

token.file
If you would like to save your OAUTH token and other auth details for use in future sessions, specify a file here. The method checks for the existence of the file and uses that if available.

auth.method
Defaults to legacy, can be set to ‘OAUTH2’ to use the newer OAUTH method.

debug.mode
Set global debug mode

endpoint
Set Adobe Analytics API endpoint rather than let RSiteCatalyst decide (not recommended)

locale
Set encoding for reports (defaults to en_US)

Details
Authorize and store credentials for the Adobe Analytics API

Value
Global credentials list ‘SC.Credentials’ in AdobeAnalytics (hidden) environment

References

The list of locale values can be obtained from the Adobe Analytics documentation:

https://marketing.adobe.com/developer/documentation/analytics-reporting-1-4/r-reportdescriptionlocale

After loading the library by library(RSiteCatalyst) command use the below command to authenticate.

SCAuth(“pheonixm.sptz:Tots”, “73ng567ygd93cf57e83ehgrteswefvaa”)

Note:It a sample for example purpose only,use your own correct user key and secret.

Sample Code :

library(“RSiteCatalyst”)

SCAuth(“Gaga:Ameri lines”,”2f40922f54f3ad116c2ca72317661b30″)

datefrom=Sys.Date()-91

dateto=Sys.Date()-1

trended_id<-QueueTrended(“productionreportsuite”,

datefrom,

dateto,

metrics = “visits”,

elements = c(“evar10″,”mobiledevicetype”),

segment.id = c(“s300000988_5be8bc302b36874afe33502f”,”s300000899_5bedfc3e706e9e558c910e1a”),

date.granularity = “day”,

interval.seconds = 300,

top = 30000

,expedite = TRUE

,enqueueOnly = TRUE

)

trended<-GetReport(trended_id, interval.seconds = 5, max.attempts = 5)

Note: RSiteCatalyst is a community-driven, open-source effort, not an official package from Adobe. As such, bug fixes and improvements rely on a vibrant community of users and developers contributing their free time and resources.

https://rdrr.io/cran/RSiteCatalyst/man/QueueDataWarehouse.html