Getting started in Attribution AI
The following guides require an understanding of the various ÃÛ¶¹ÊÓƵ Experience Platform services involved with using Attribution AI. Before beginning the tutorials, please review the following documents:
- Experience Data Model (XDM) System overview: XDM is the foundational framework that allows ÃÛ¶¹ÊÓƵ Experience Cloud, powered by Experience Platform, to deliver the right message to the right person, on the right channel, at exactly the right moment. The methodology on which Experience Platform is built, XDM System, operationalizes Experience Data Model schemas for use by Platform services.
- Basics of schema composition: This document provides an introduction to Experience Data Model (XDM) schemas and the building blocks, principles, and best practices for composing schemas to be used in ÃÛ¶¹ÊÓƵ Experience Platform.
- Building schemas: This tutorial covers the steps for creating a schema using the Schema Editor within Experience Platform.
Attribution AI requires datasets to conform to the Consumer Experience Events (CEE) schema, which is an Experience Data Model (XDM) schema field group. Please contact ÃÛ¶¹ÊÓƵ support at attributionai-support@adobe.com in order to implement or make changes to this data. If media spend data is present, you can do further analysis such as incremental revenue and ROI. If customer profile data is available, you can further attribute credits to the customer profile level.
Terminology
-
Conversion event: Any digital event or digital interaction that customers do to indicate a milestone towards a goal, such as conference registrations. Additional examples include paid conversions, free account sign-ups, or qualifying for a trait.
-
Touchpoint: Any digital event or digital interaction that customers do in the path towards a goal. Examples include before-purchase-related marketing efforts, display advertising impressions viewed, and paid search clicks.
Downloading Attribution AI scores
Downloading Attribution AI scores is done through a combination of API calls. In order to make calls to Platform APIs, you must first complete the . Completing the authentication tutorial provides the values for each of the required headers in all Experience Platform API calls, as shown below:
- Authorization: Bearer
{ACCESS_TOKEN} - x-api-key:
{API_KEY} - x-gw-ims-org-id:
{ORG_ID}
All resources in Experience Platform are isolated to specific virtual sandboxes. All requests to Platform APIs require a header that specifies the name of the sandbox the operation will take place in:
- x-sandbox-name:
{SANDBOX_NAME}
Reading sample API calls
This guide provides example API calls to demonstrate how to format your requests. These include paths, required headers, and properly formatted request payloads. Sample JSON returned in API responses is also provided. For information on the conventions used in documentation for sample API calls, see the section on how to read example API calls in the Experience Platform troubleshooting guide.
Access control access-control
When using role-based access control, the View Attribution AI and Manage Attribution AI privileges grant access to different functionalities of Attribution AI. The Manage Attribution AI lets you create, clone, edit, delete, enable, or disable an instance while View Attribution AI lets you read or view it. The create, edit and delete actions are recorded by audit logs.
See the documentation to learn assigning permissions for access control or how to use audit logs to monitor access and activity.
Next steps next-steps
Once you are ready and have all your credentials and schemas in place, start by following the Attribution AI user interface guide. This guide walks you through creating an instance and submitting it for training and scoring.