Offline conversions Yandex Metrica for OpenCart 3

Why is it needed

The store counts conversions using a counter on the “Thank you for your order” page. Because of this, Direct’s auto strategies are trained on the fact of placing an order - and do not know that a third of orders are canceled, not redeemed, or returned. The budget goes into traffic, which brings in applications, but does not bring in money.

The module sends an offline conversion to Metrica when the order is actually paid or completed, and transmits the value along with it: the order amount or margin. The strategy begins to optimize for redemption, and not for pressing a button.


Interception on server

• yclid comes in the address of the landing page from a click on the ad and is available from PHP to for processing any JavaScript.
• It exists even where the counter is blocked by a browser extension and the ClientID has not been generated at all.
• The order is counted even if the client paid on the acquiring side and did not return to the “Thank you” page.

The client counter does not see such visits at all, but the server does.


What can do

• Attribution interception. yclid, ymclid, gclid, all utm tags, referrer and landing page. ClientID is read from the cookie counter.
• Photograph to order. Identifiers are fixed at the time of registration and do not change: subsequent client visits do not rewrite the history.
• Order statuses and goals Metrics. “Paid” → order_paid, “Completed” → order_completed, “Canceled” → order_canceled. You can create several rules for one status.
• Conversion value. Order total, amount without delivery, specified share of the amount (rough margin), value from the order field (cost from 1C), fixed value or zero.
• No duplicates. One order for one purpose goes once, and this keeps a unique index in the database, and not a check in the code.
• Repetitions in case of failures. Network errors and 5xx are repeated according to an increasing schedule: 5 minutes, 30 minutes, 2 hours, 6 hours, day. Invalid token uploadstops immediately and without repetitions.
• Download control. The module polls the Metrica to the final status and shows what is counted and what is not matched.
• Multi-store. Own counter and token for each store.

Administrator

• Setup Wizard - step by step from an application in Yandex OAuth to a task in the crown, with direct links.
• Diagnostics - checklist: is the token valid, is offline conversions included in the counter, are there goals, when was the crown spent, what share of orders is attributed in 30 days. Plus a list of orders withoutattribution.
• Queue - filters by status, order, purpose and dates, mass reshipment.
• Download log - download number, how many lines were sent and how many were received by Metrica, final status, API response.
• Tab “Order Source” on the order card: yclid, ClientID, utm tags, landing page, referrer and conversions sent for the order with statuses.
• Buttons “Check connection”, “Create goals in Metrica” and manual launch of cron - the setting is visible immediately, and not after twenty minutes.

Personal data

The module does not transfer to Metrica Full Name,phone, email and address. Only the click or visit ID, goal ID, time and amount are left. The OAuth token is not logged under any circumstances.


Restrictions

• Metrica attribution window is 21 days. With a long transaction cycle (furniture, equipment, B2B), part of the payments will go out of the window; The module marks such conversions as missed and does not send them empty.
• A sent conversion cannot be recalled - this is a limitation of Metrica. Therefore, sending is tied to terminal statuses, and status rollback is compensated by a separate cancellation goal. The interface warns about this.

Technical details

• Versionmodule: 1.0
• Compatibility: OpenCart 3.0.x, ocStore 3.0.x. Tested on PHP 8.3, requires cURL.
• Standard installation: loading the ocmod archive, updating modifiers, activating the module.
• Works on OpenCart events, the core is not patched. The modifier only affects the interface: menu item and tab on the order card.
• It doesn’t touch its own tables in the database, other people’s UTM trackers.
• Cron: HTTP address with a secret or run from the command line. Parallel launch protection, passage time limitation.
• Languages: Russian and English.

What's new in version 1.0

• First release.

Write a review

Your Name:


Your Review: Note: HTML is not translated!

Rating: Bad           Good

Enter the code in the box below: