Skip to content

Commit 3b2e452

Browse files
committed
merge master
2 parents 3327e22 + 3b5ff12 commit 3b2e452

File tree

2 files changed

+23
-2
lines changed

2 files changed

+23
-2
lines changed

src/connections/destinations/catalog/google-analytics/ga4-plans.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ If you decide to use GA4 so you can compare the data, you should spend some time
2828

2929
GA4’s out-of-the-box reports are different from UA’s. GA4’s reporting is much more configurable, and supports new reporting metrics like churn probability and predictive revenue estimates.
3030

31-
You might not be able to perfectly recreate your UA reports in GA4. One approach is to send your data to both UA and G4A while you build out your new reports in G4A, and improve those reports over time. Once you are satisfied that your G4A reports meet your needs, you can gradually migrate away from using the original reporting in UA.
31+
You might not be able to perfectly recreate your UA reports in GA4. One approach is to send your data to both UA and GA4 while you build out your new reports in GA4, and improve those reports over time. Once you are satisfied that your GA4 reports meet your needs, you can gradually migrate away from using the original reporting in UA.
3232

3333

3434
## Client-based or server-based

src/connections/destinations/catalog/pinterest-audiences/index.md

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,20 @@ For more information about advertising with Pinterest, see:
1414
- A Pinterest Ads account with the `owner`, `admin`, or `audience_manager` role
1515

1616
**Supported identifiers**
17+
<<<<<<< HEAD
1718
- email
19+
=======
20+
- Email
21+
>>>>>>> master
1822
- iOS IDFA
1923
- Android ID
2024

2125
> warning ""
26+
<<<<<<< HEAD
2227
> **Note**: The Segment iOS SDK version 4.0 and up does not collect automatically collect IDFA. For more information, see the [iOS 14 Guide](docs/connections/sources/catalog/libraries/mobile/ios/ios14-guide/).
28+
=======
29+
> **Note**: The Segment iOS SDK version 4.0 and up does not collect automatically collect IDFA. For more information, see the [iOS 14 Guide](/docs/connections/sources/catalog/libraries/mobile/ios/ios14-guide/).
30+
>>>>>>> master
2331
2432
**Connection type**
2533
- Server-side
@@ -39,15 +47,28 @@ The Pinterest Audiences destination syncs data from Segment Personas to Pinteres
3947
3. The configured Pinterest Audiences destination should appear in the Send as User List category of available destinations.
4048
4. Select the destination, and click Add Destination.
4149

50+
<<<<<<< HEAD
4251
## FAQ
4352

4453
### What does the audience size represent?
4554
It's the final count of matched users - so the actual targetable audience size.
4655
The audience size represented in Segment is the final count of matched users between your customer profiles in Segment and Pinterest users. This number denotes your targetable audience size within Pinterest.
56+
=======
57+
The initial synchronization of audience data may take several hours, depending on the size of the audience. Once the initial sync occurs, you'll see a new audience in the Pinterest Audiences dashboard.
58+
59+
## FAQ
60+
61+
### What does the audience size represent?
62+
The audience size represented in Pinterest is the final count of matched users between your customer profiles in Segment and Pinterest users. This number denotes your targetable audience size within Pinterest.
63+
>>>>>>> master
4764
4865
The initial synchronization of audience data may take several hours, depending on the size of the audience. Once the initial sync occurs, you’ll see a new Audience in the Pinterest Audiences dashboard.
4966

5067
### Are lists/audiences processed on some interval, or on customer list update? Do we need to wait 24-48 hours every time we add/remove identifiers from a list?
5168
Processing happens regularly and automatically throughout the day - but can take up to 24 hours.
5269

53-
You do not need to wait to continue sending data; however, any campaigns using those audiences will not see the changes until after processing (they'll continue running against whatever users have already been matched).
70+
<<<<<<< HEAD
71+
You do not need to wait to continue sending data; however, any campaigns using those audiences will not see the changes until after processing (they'll continue running against whatever users have already been matched).
72+
=======
73+
You do not need to wait to continue sending data; however, any campaigns using those audiences will not see the changes until after processing (they'll continue running against whatever users have already been matched).
74+
>>>>>>> master

0 commit comments

Comments
 (0)