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-pinterest-conversions-api/index.md
+83-1Lines changed: 83 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,7 @@ The Pinterest Conversions API destination provides the following benefits :-
29
29
-**Fewer settings**. Data mapping for actions-based destinations happens during configuration, which eliminates the need for most settings.
30
30
-**Clearer mapping of data**. Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to Pinterest Conversions API.
31
31
-**Prebuilt mappings**. Mappings for standard Pinterest Conversions API events, like `Add to Cart`, are prebuilt with the prescribed parameters and available for customization.
32
+
-**Support Deduplication**. Deduplication removes duplicates events which improves the accuracy of your conversions
32
33
-**Support for page calls**. Page calls can be sent to Pinterest as a standard Page View.
33
34
-**Support for multi-user arrays**. User data nested within arrays, like the `User Data` array in the Order Completed event, can be sent to Pinterest.
34
35
-**Data normalization**. Data is normalized before it is hashed to send to Pinterest Conversions.
@@ -45,6 +46,21 @@ By using deduplication advertisers can report conversions using both the tag and
45
46
46
47
Advertisers should use deduplication for any events they expect to be reported by multiple sources across the API and the Pinterest Tag.
47
48
49
+
## Limited Data Processing
50
+
Starting from Jan 1, 2023, Pinterest introduced the Limited Data Processing flag as per California Consumer Privacy Act (CCPA). With this flag set Pinterest will allow advertisers to comply with CCPA.
51
+
52
+
Advertisers are responsible for complying with user opt-outs, as well as identifying the user’s state of residency when implementing the Limited Data Processing flag.
53
+
54
+
Keep in mind that the Limited Data Processing flag could impact campaign performance and targeting use cases. Pinterest recommends using the Limited Data Processing flag on a per-user basis for best results.
55
+
56
+
LDP relies on 3 fields and is enabled only when all 3 combinations are met, if one of them is not met then LDP is disabled / ignored.
57
+
58
+
| Field Name | Field Description | Required Value for LDP |
| opt_out_type | Opt Out Type based on User’s privacy preference| "LDP" |
61
+
| st | State of Residence | "CA" |
62
+
| country | Country of Residence | "US" |
63
+
48
64
## Getting started
49
65
50
66
Before connecting to the Pinterest Conversions destination, you must have a [Pinterest](https://ads.pinterest.com/login/){:target="_blank"} account and an Ad Account ID.
@@ -65,4 +81,70 @@ To connect the Pinterst Conversions API Destination:
65
81
9. Finally, enable the destination using the **Enable Destination** toggle switch and click **Save Changes**.
66
82
67
83
68
-
{% include components/actions-fields.html settings="true"%}
84
+
{% include components/actions-fields.html settings="true"%}
85
+
86
+
## FAQ & Troubleshooting
87
+
88
+
### PII Hashing
89
+
90
+
Segment creates a SHA-256 hash of the following fields before sending to Facebook:
91
+
- External ID
92
+
- Mobile Ad Identifier
93
+
- Email
94
+
- Phone
95
+
- Gender
96
+
- Date of Birth
97
+
- Last Name
98
+
- First Name
99
+
- City
100
+
- State
101
+
- Zip Code
102
+
- Country
103
+
104
+
### User Data Parameters
105
+
106
+
Segment automatically maps User Data fields to their corresponding parameters [as expected by the Conversions API](https://developers.pinterest.com/docs/conversions/best/#Authenticating%20for%20the%20Conversion%20Tracking%20endpoint#The%20%2Cuser_data%2C%20and%20%2Ccustom_data%2C%20objects#Required%2C%20recommended%2C%20and%20optional%20fields#Required%2C%20recommended%2C%20and%20optional%20fields#User_data%2C%20and%20%2Ccustom_data%2C%20objects){:target="_blank"} before sending to Pinterest Conversions:
107
+
108
+
| User Data Field | Conversions API User Data Parameter |
Segment automatically maps Custom Data fields to their corresponding parameters [as expected by the Conversions API](https://developers.pinterest.com/docs/conversions/best/#Authenticating%20for%20the%20Conversion%20Tracking%20endpoint#The%20%2Cuser_data%2C%20and%20%2Ccustom_data%2C%20objects#Required%2C%20recommended%2C%20and%20optional%20fields#Required%2C%20recommended%2C%20and%20optional%20fields#User_data%2C%20and%20%2Ccustom_data%2C%20objects){:target="_blank"} before sending to Pinterest Conversions:
128
+
129
+
| User Data Field | Conversions API Custom Data Parameter |
Pinterest requires the `action_source` server event parameter for all events sent to the Pinterest Conversions API. This parameter specifies where the conversions occur.
143
+
144
+
### Verify Events in Pinterest Conversions Dashboard
145
+
146
+
After you start sending events, you should start seeing them in dashboard. You can confirm that Pinterest received them:
147
+
148
+
1. Go to the Events Overview.
149
+
2. Click on the Event History to see all the events sent to pinterest conversions.
0 commit comments