An online store, connected orders and clearer campaign measurement.

The store operated in a competitive category. Its website and measurement tools had developed in stages, and order reporting was inconsistent: some purchases were missing while others appeared more than once.

For the team deciding the budget, the issue was straightforward. If order counts or values are wrong, an ad can look stronger or weaker than it is. The commercial objective was profitable growth; the work needed to connect the store, order management and advertising.

The store migrated from WordPress to Shopify, using a premium theme customized for the client. Shopify is the platform used to manage products and online purchases.

A custom integration connected the store to its CRM, the system used by the business to manage commercial information. It linked stock, order and invoice workflows.

An order placed on the website is also work for the team processing it. Connecting these systems was intended to support that flow, so the store and operations could work with related information.

The setup included server-side tracking: part of the transmission of purchase-event data is handled through a server. Its purpose was to reduce the inconsistencies that made campaign evaluation difficult.

A conversion here means a tracked action, such as completing an order. Reporting the same order twice can overstate advertising performance. Missing it can understate performance.

This implementation does not mean every sale can be linked to an ad with certainty. User consent, configuration and the rules platforms use to assign credit for orders still affect reporting.

Advertising included campaigns to attract buyers and campaigns for searches containing the store’s name. These serve different situations.

The former aim to bring interest to the offer. In the latter, the person already knows the store and is looking for it. A strong result from branded searches therefore does not automatically prove the ad created a new customer.

Separating these roles supports a useful question: which part of the budget attracts demand, and which part responds to interest that already exists?

Campaigns included category and generic searches alongside seasonal promotions such as summer sun protection and Black Friday. Sought-after brands helped attract interest, while product selection also took margin into account.

Product lists used in Shopping ads were supported by the integration with the commercial system. Visuals were adapted to promotional periods so the advertising matched the featured offer.

The store, stock, orders and invoices were connected in a shared flow. The team had infrastructure for following a website purchase through commercial processing, while campaigns had a rebuilt measurement setup.

The concrete change was the connection between sales, operations and promotion. The information available for this case study does not establish a verified profit uplift or a quantified reduction in errors.

For advertising evaluation, ROAS means the value of sales attributed to ads divided by advertising spend. A purely explanatory example, not a result from this project: €300 in attributed sales from €100 in ad spend gives a ROAS of 3.

ROAS is not profit. Product costs, discounts, delivery and other expenses must also be considered before deciding whether to increase the budget.

If the store shows one order count and advertising platforms show another, it is worth checking why. If stock and order information is difficult to move between systems, the issue may involve both the website and operations.

This project shows why the platform, data and campaigns need to be considered together. Advertising decisions depend on what the store can sell, process and measure.