From acbe6216407ef1fba2e3029d88197ae7412791a4 Mon Sep 17 00:00:00 2001 From: Terence Ma Date: Fri, 13 Sep 2024 16:30:37 +1000 Subject: [PATCH 1/2] add detail on linkedin capi --- .../catalog/actions-linkedin-conversions/index.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-linkedin-conversions/index.md b/src/connections/destinations/catalog/actions-linkedin-conversions/index.md index 699679051e..48144c54e8 100644 --- a/src/connections/destinations/catalog/actions-linkedin-conversions/index.md +++ b/src/connections/destinations/catalog/actions-linkedin-conversions/index.md @@ -43,6 +43,9 @@ Your inputs must meet the following criteria: - `LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID` - `ACXIOM_ID` - `ORACLE_MOAT_ID` -- `conversionHappenedAt` must be a valid timestamp (milliseconds since epoch) and must have happened in the past 90 days +- `conversionHappenedAt` must be a valid epoch timestamp (milliseconds since epoch) and must have happened in the past 90 days. Segment additionally accepts [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) formatted timestamp, and converts it to valid epoch timestamp value. Any deviations from this specification might lead to failed inputs. + +### Why LinkedIn still shows "no integration data" after I successfully sent the data? +LinkdedIn won't reject events due to the lack ofcurrency and amount data, but they will not correctly recogonize the events you sent via Segment. Please ensure your payload has the data or try "Validate" for other undocumented errors. From 85f9c77383d47bfb5bb2a8fdbbbd32bcb00e2ef3 Mon Sep 17 00:00:00 2001 From: Terence Ma Date: Fri, 13 Sep 2024 16:46:57 +1000 Subject: [PATCH 2/2] fix wording --- .../catalog/actions-linkedin-conversions/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-linkedin-conversions/index.md b/src/connections/destinations/catalog/actions-linkedin-conversions/index.md index 48144c54e8..351255b4f7 100644 --- a/src/connections/destinations/catalog/actions-linkedin-conversions/index.md +++ b/src/connections/destinations/catalog/actions-linkedin-conversions/index.md @@ -43,9 +43,9 @@ Your inputs must meet the following criteria: - `LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID` - `ACXIOM_ID` - `ORACLE_MOAT_ID` -- `conversionHappenedAt` must be a valid epoch timestamp (milliseconds since epoch) and must have happened in the past 90 days. Segment additionally accepts [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) formatted timestamp, and converts it to valid epoch timestamp value. +- `conversionHappenedAt` must be a valid epoch timestamp (milliseconds since epoch) and must have happened in the past 90 days. Segment additionally accepts [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601){:target="_blank"} formatted timestamps, and converts it to a valid epoch timestamp. Any deviations from this specification might lead to failed inputs. ### Why LinkedIn still shows "no integration data" after I successfully sent the data? -LinkdedIn won't reject events due to the lack ofcurrency and amount data, but they will not correctly recogonize the events you sent via Segment. Please ensure your payload has the data or try "Validate" for other undocumented errors. +LinkdedIn won't reject events due to the lack of currency and amount data, but they will not correctly recogonize the events you sent via Segment. Please ensure your payload has the data or try [Event Tester](/docs/connections/test-connections/#ensuring-an-event-is-successfully-making-it-to-a-specific-destination) for other causes.