[IMP]google_tag_manager_advanced_tracking, facebook_pixel_tracking

[fw-bot-adhoc]

google_tag_manager_advanced_tracking:

• Shipping and discount separated from product items in GTM events
• Reward lines filtered from items, accumulated as discount
• Replaced legacy Python-dict string parsing with standard JSON.parse

facebook_pixel_tracking:

• Migrated all events to current Meta Pixel standard (content_ids, contents, currency, value)
• Fixed critical bug: Purchase event was not being fired (missing event name)
• Delivery and reward lines excluded from contents

website_sale_advanced_tracking (shared):

• prepare_purchase_information: delivery/reward lines separated; returns json.dumps()
• prepare_checkout_information: added is_reward_line flag; item_name uses product name; returns json.dumps()
• Template: data-product_id on add_to_cart now uses product.id (always present) instead of default_code

Forward-Port-Of: #451

[roboadhoc]

[fw-bot-adhoc]

@JrAdhoc @cem-adhoc cherrypicking of pull request #451 failed.

stdout:

CONFLICT (modify/delete): facebook_pixel_tracking/static/src/js/website_sale_tracking.js deleted in e9aa8e7dd3e7f495758de7710f7b5500db4fb4ca and modified in e7ed3d553e640efbe0aedd33f438214083ef1525.  Version e7ed3d553e640efbe0aedd33f438214083ef1525 of facebook_pixel_tracking/static/src/js/website_sale_tracking.js left in tree.
Auto-merging google_tag_manager_advanced_tracking/static/src/interactions/website_sale_tracking.js
CONFLICT (content): Merge conflict in google_tag_manager_advanced_tracking/static/src/interactions/website_sale_tracking.js
Auto-merging website_sale_advanced_tracking/views/templates.xml

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

you can use git-fw to re-do the forward-port for you locally.

⚠️ after resolving this conflict, you will need to merge it via @roboadhoc.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[fw-bot-adhoc]

@JrAdhoc @cem-adhoc this forward port of #451 is awaiting action (not merged or closed).

[fw-bot-adhoc]

@JrAdhoc @cem-adhoc this forward port of #451 is awaiting action (not merged or closed).

[fw-bot-adhoc]

@JrAdhoc @cem-adhoc this forward port of #451 is awaiting action (not merged or closed).

[fw-bot-adhoc]

@JrAdhoc @cem-adhoc this forward port of #451 is awaiting action (not merged or closed).

[JrAdhoc]

Resolved the forward-port merge conflicts in the two tracking JS files.

Since 19.0 already migrated both modules to the interaction framework (static/src/interactions/) while #451 was on the legacy public_widget (static/src/js/), this was not a plain marker removal:

• google_tag_manager_advanced_tracking: 19.0 already carried most of [IMP]google_tag_manager_advanced_tracking, facebook_pixel_tracking #451's logic; resolved the 3 conflict hunks keeping the 19.0 structure.
• facebook_pixel_tracking: the 19.0 interactions/ file predated [IMP]google_tag_manager_advanced_tracking, facebook_pixel_tracking #451, so I ported [IMP]google_tag_manager_advanced_tracking, facebook_pixel_tracking #451's behavioral changes into it (sku/currency, JSON parsing, contents/num_items, reward filtering) and removed the stray legacy static/src/js/website_sale_tracking.js the bot left behind. Preserved 19.0-only bits (the /shop/cart guard and the .o_website_sale_checkout_container selector).

Out of forward-port scope — heads up: I also simplified submitForm (start_payment) in GTM, dropping the legacy Python-dict regex sanitization in favor of JSON.parse, consistent with the rest of the PR now that the backend returns json.dumps(). The regex would actually corrupt valid JSON containing apostrophes. It was pre-existing 19.0 code untouched by the conflict, flagging it here since it's beyond the strict FW port.

pre-commit (incl. check-merge-conflict) passes on all files.