[SNAPWOO-76] Snapchat for WooCommerce shows low transaction ID overlap between Pixel and CAPI purchase events#63
Open
jamesmorrison wants to merge 2 commits intotrunkfrom
Conversation
…hase deduplication.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes proposed in this Pull Request:
Closes https://linear.app/a8c/issue/SNAPWOO-76/snapchat-for-woocommerce-shows-low-transaction-id-overlap-between
Screenshots:
N/A
Detailed test instructions:
Test 1: Pixel PURCHASE event uses order ID
Test 2: CAPI PURCHASE event uses order ID
Test 3: Duplicate tracking guard still works
snaptr("track", "PURCHASE"call should not appear a second time (blocked by the _snapchat_pixel_tracked meta flag).Test 4: Non-purchase events are unaffected
Additional details: