Skip to content

Add section about conversion tracking with LinkedIn Insight Tag #5587

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 3, 2023

Conversation

sarahrudy
Copy link
Contributor

Proposed changes

  • Added section letting customers know that our LinkedIn Insight Tag destination is different from our other destinations in that all Segment does is load the Insight tag onto their website for them allowing them to call native methods and that any special conversion tracking would need to be done within their LinkedIn workspace, as they normally would if they were setting up LinkedIn without Segment.

Merge timing

  • ASAP once approved

@sarahrudy sarahrudy added the KCS label Oct 25, 2023
@sarahrudy sarahrudy changed the title Add section about tracking conversions with LinkedIn Insight Tag Add section about conversion tracking with LinkedIn Insight Tag Oct 25, 2023
- change "tracking conversions" to "conversion tracking"
@sarahrudy sarahrudy marked this pull request as ready for review November 2, 2023 19:24
@sarahrudy sarahrudy requested a review from a team as a code owner November 2, 2023 19:24
@sarahrudy sarahrudy requested review from stayseesong and removed request for a team November 2, 2023 19:24
@stayseesong stayseesong merged commit 68f7a1f into develop Nov 3, 2023
@stayseesong stayseesong deleted the sarahrudy-patch-8 branch November 3, 2023 19:46
Copy link
Contributor

github-actions bot commented Nov 3, 2023

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants