You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-amazon-conversions-api/index.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ Amazon requires at least one match key to identify the user associated with each
89
89
| postalCode | User's postal code (is hashed) |
90
90
| maid | Mobile advertising ID (ADID, IDFA, or FIREADID) |
91
91
| rampId | RAMP ID for attribution to traffic events |
92
-
| matchId | Match ID is an anonymous opaque unique identifier that represents a user on an advertiser’s system, like loyalty membership ID and order ID. With Match ID, advertisers can accurately track campaign performance without sharing customer data to Amazon like hashed email/phone while navigating complex customer journeys that spans multiple channels and devices. The advertisers implementing Amazon Advertising Tag (AAT) on their website can send match_id as an attribute along with the online events. Amazon matches this to users via cookies or hashed PII. When these users convert offline, advertisers can report it through Conversions API (CAPI) using the same match_id |
92
+
| matchId | Match ID serves as an anonymous, opaque unique identifier that corresponds to individual users within an advertiser's system, such as loyalty membership identifications and order references. This functionality enables advertisers to precisely monitor campaign effectiveness while maintaining customer data privacy, eliminating the need to share sensitive information like hashed email addresses or phone numbers with Amazon, particularly when analyzing complex customer journeys across multiple channels and devices. The advertisers who implement the Amazon Advertising Tag (AAT) on their websites can transmit match_id as a parameter in conjunction with online event tracking. Amazon's system subsequently correlates these identifiers with users through cookies or hashed Personally Identifiable Information (PII). In instances where users complete offline conversions, advertisers can report these activities through the Conversions API (CAPI) utilizing the corresponding match_id, ensuring seamless cross-channel attribution. |
93
93
94
94
Segment automatically maps these fields from standard identity traits when available.
95
95
@@ -164,15 +164,15 @@ Personally identifiable information (PII) fields like email, phone, name, and ad
164
164
165
165
After you start sending events, you should see them in your Amazon Advertising dashboard under conversion tracking reports. Allow some time for the events to be processed and attributed.
166
166
167
-
#### Which advertising accounts can access Amazon Conversions API?
167
+
#### Which advertising accounts can access Amazon Conversions API through Segment?
168
168
169
169
- Self-Service (SS) Accounts: Yes
170
170
- Managed Service (MS) Accounts: No
171
-
- Manager Accounts (MA): Not yet, but we can add if there is enough demand
171
+
- Manager Accounts (MA): At present, this functionality is not available. However, we are actively monitoring market demand and user requirements. Should sufficient interest emerge from our user base, we will evaluate the possibility of implementing this feature in a future release.
172
172
173
173
#### I am an advertiser on Amazon Demand Side Platform. My agency cannot provide access to their entity as they manage other clients. How do I get access to a specific advertiser account?
174
174
175
175
-**Option 1**:
176
-
1.Ask the agency to provide access to the specific advertiser account (where they wish to run your campaigns) within their agency. Events Manager must be given ‘View and Edit’ permission. Please see help article [here](https://advertising.amazon.com/help/G3ZZ6ZXQWG34DPPM){:target="_blank"}.
177
-
2.Use the Amazon Conversions API to send data to the specific account they have been given access to in step #1.
178
-
-**Option 2**: [Not a supported pattern via Segment yet]Upload your data directly to Manager Account. You will see the data in Data Manager. You can then share the data from Data Manager to other advertiser accounts linked to the Manager Account. Learn more [here](https://advertising.amazon.com/API/docs/en-us/adm/1_ads-data-manager-console-overview){:target="_blank"}.
176
+
1.Please request your agency to grant access to the specific advertiser account intended for campaign execution. Specifically, 'View and Edit' permissions must be assigned for Events Manager. Please see help article [here](https://advertising.amazon.com/help/G3ZZ6ZXQWG34DPPM){:target="_blank"}.
177
+
2.Utilize the Amazon Conversions API (CAPI) to transmit data to the advertiser account for which access was granted in the previous step.
178
+
-**Option 2**: [Not a supported pattern via Segment yet]Please upload your data directly to the Manager Account, where it will be visible in Ads Data Manager. Once uploaded, you can efficiently share this data with other advertiser accounts that are linked to your Manager Account. Learn more [here](https://advertising.amazon.com/API/docs/en-us/adm/1_ads-data-manager-console-overview){:target="_blank"}.
0 commit comments