The sale was happening. The origin was lost along the way.
The company advertised on Google and Meta, received website and online store visits, and also made sales through its sales team. A company could find an ad, request a quote, and only then place an order. This revenue was not tracked by the campaign.
The data existed, but each area only saw a part of it. Google Analytics showed the traffic; the CRM, the sales tracking system, stored the quotes; and the ERP, the company's management system, recorded what had been invoiced. The monthly report gathered information into a closed presentation, without resolving the connection between the different pieces of data.
the work of Bytebio It began with defining what counts as a sale coming from digital channels and how to recognize that sale across systems.
To measure sales, it was necessary to preserve the origin.
First Bytebio He organized the naming convention for advertisements to distinguish between B2B (business-to-business) and B2C (consumer-to-consumer). Each sales channel now has its own return, instead of a single number encompassing both operations.
Next, he structured the UTMs, the parameters in the link that identify the origin of the visit, including a dedicated field for the keyword. When a company requested a quote through the website, the origin of the click was recorded along with the company's tax ID number. This link allowed subsequent revenue to be associated with the campaign that generated the opportunity.
To make the information flow, we developed APIs, connections through which systems exchange data. Advertisements, website, online store, CRM, ERP, and newsletter began to feed into a consolidated database, used by marketing and sales dashboards.
- Click on the ad.
Campaign, term, and type recorded in UTM.
- Quote via website
The CNPJ (Brazilian tax ID) is linked to the origin of the click.
- Sale invoiced in the ERP system.
The revenue goes back to the same source.
- Updated campaign ROAS
B2B and B2C separated by the ad name.