Page Comparison

...

GOAL: Initial calls focused around unifying Pardot data and coming up with a Knoema match logic for Adobe ↔︎ Pardot. End Goal Still TBDNEW

MATCHING: Relays on the “Pardot Cookie (Visitor ID)” and “prospect_id” and “ECID“. The “ECID” is the adobe ID, which can have multiple identifying events. The data also suffers from false positives on identifying/matching. This is due to Forwarding.

Forwarding is when the user who is sent the email (email creates identifying events) forwards the email on to someone who triggers the link/identifying event. This causes the tacking to be incorrect and adobe web page views data is assigned to wrong individual. Can be solved by profiling the IP address flows to identify Alliance Bernstein traffic (client forward back to Alliance Bernstein).

https://docs.google.com/spreadsheets/d/13d-n2k1xJ_DGTc0OdQnTMx4H_eVG_RXTnBe7HLE5SSs/edit#gid=0

File Type: Full File (Overwrite)

...

(HISTORICAL INFO)

OLD: Sample Data Provided by Alliance Bernstein.

OLD Data Objects:

1. Adobe.csv

2. AdvisorList.csv (key: AeEntityID)

3. AdvisorListSalesAUM.csv (key: AeEntityID)

4. ClientEngagement.csv ((key: AeEntityID))

5. RM_RC_YTD_ACTIVITY.csv (key: AeEntityID)

6. BuyingUnits.csv (key: AeEntityID)

...

“AeEntityId” attribute looks to be common key across all but “Adobe.csv”. (HISTORICAL INFO)

OLD: Sample Cut. Jira = https://knoema.jira.com/browse/CLI-42324?atlOrigin=eyJpIjoiNjRmNTI4YmIzYjBjNDAwZDljZWRjYTlmZmUwNWQxYTYiLCJwIjoiaiJ9

...