Skip to content

Adobe alignment #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update README.md
  • Loading branch information
cooperreid-optimizely authored Mar 6, 2019
commit 9f2808d4247d734faed3d3612efc375889195d33
14 changes: 14 additions & 0 deletions Integrations/Analytics/Adobe Analytics/Alignment/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Aligning Adobe Analytics with Optimizely Results
For organizations where alignment is critical, there are a few technical considerations and adjustments to make in order to best align to metrics in the two systems.

Misalignment can always be traced back to _when_ the two client tools are dispatching the impressions/conversions back to their respective servers.

This challenge can be solved by aligning the two event calls as closely as possible.

Optimizely offers the [hold/send API](https://help.optimizely.com/Set_Up_Optimizely/Control_the_timing_of_Optimizely_X_Web_Event_dispatch_with_holdEvents_and_sendEvents) for managing this.

## Two scenarios

### Adobe Loaded Ahead of Optimizely Snippet

### Adobe not guaranteed to load ahead of Optimizely Snippet