--- title: "Offline conversions for Google Ads, Meta and TikTok" summary: "VenueX sends a retailer's store sales to Google Ads, Meta and TikTok every day, with personal data hashed with SHA-256, and reports offline ROAS next to online ROAS where the platform supports it." canonical_url: https://venuex.io/platform/offline-conversions lang: en alternate: tr: https://venuex.io/tr/platform/offline-conversions.md last_updated: 2026-10-28 type: product-module --- > Site index: https://venuex.io/llms.txt > > Türkçe: https://venuex.io/tr/platform/offline-conversions.md # Online-to-offline measurement Online-to-offline measurement is the VenueX module that sends a retailer's store sales to Google Ads, Meta and TikTok every day through their official APIs. The brand hashes the email addresses, phone numbers and names in each sale with SHA-256 before sending them, and the ad platforms match the sales to people their ads reached. The brand then sees store sales and offline ROAS next to online ROAS, by platform and campaign, where the platform supports it. Page: https://venuex.io/platform/offline-conversions ## Who it is for Multi-location retailers that sell in physical stores and advertise on Google, Meta or TikTok. The main users are marketing teams that must show management what campaigns bring to the stores. ## The problem it solves Shoppers often see an ad online and then buy in a store. By default, the ad platforms see only online conversions, so the ad report leaves store sales out. As a result: - Campaigns that look weak on online results get switched off, even when they drive store sales. - Management asks what digital marketing brings to the stores, and the team has no number to show. - Online ROAS alone makes digital look weaker than it is when the next budget is set. ## How it works 1. **Agree the data.** The brand and VenueX agree which fields the sales file contains and when it arrives. The brand's legal team approves the data flow. 2. **Connect the ad accounts.** The brand gives VenueX access to its Google Ads, Meta and TikTok ad accounts. The accounts stay owned by the brand. 3. **Send the day's sales.** The POS or CRM sends store sales by SFTP, API or file. The brand hashes email, phone and name with SHA-256 before sending them. 4. **Check.** VenueX checks formats and store codes, and fixes errors before upload. VenueX does not receive raw contact data. 5. **Upload.** VenueX uploads the sales to each platform every day through its official API, and fixes upload errors. 6. **Match.** Each platform matches the hashed sales to people its ads reached, under its own rules. The platforms do the matching, not VenueX. 7. **Report.** VenueX reads the results back and shows store sales and offline ROAS next to online ROAS, by platform and campaign. The VenueX team runs steps 4 to 7. Setup usually includes a backfill of up to 90 days of past sales, within each platform's limits for older data. In the public success stories, Koçtaş was connected in 4 weeks and Karaca in 3 weeks from kickoff. After the first uploads, the platforms need some weeks of data before results settle. ## Data VenueX needs | Field | Required | Notes | |---|---|---| | Sale value | Yes | The amount of the transaction. | | Store code | Yes | Must match the store codes VenueX holds for each store. | | Date and time | Yes | When the sale happened. | | Email, phone and name | Yes, for matching | Hashed with SHA-256 by the brand before sending. | | Product or basket lines | No | Optional. | | Customer ID | No | Optional. | ## Platforms | Platform | What VenueX manages | Notes | |---|---|---| | Google Ads | Daily store sales uploads | Results appear in the brand's Google Ads account and in VenueX. Google may report part of them as modelled estimates. | | Meta | Daily store sales uploads to the brand's Meta dataset | Results appear in Meta Ads Manager and in VenueX. | | TikTok | Daily store sales uploads | Ads only. VenueX does not manage store presence on TikTok. | Each platform reports under its own rules, limits and attribution settings. ## What the brand sees - Store sales and offline revenue by platform and campaign. - Offline ROAS next to online ROAS, where the platform supports it. - Campaign spend, impressions and clicks next to the store results. - Upload status for each platform: last upload, records sent and open issues. - For each result, the platform that reported it. ## Data protection and access - The brand hashes email, phone and name with SHA-256 before sending them. VenueX does not receive raw contact data. - Hashed identifiers are pseudonymised, not anonymous. They are still personal data under KVKK and GDPR, so the brand's legal team approves the data flow. - VenueX acts as a data processor under KVKK and GDPR. A data processing agreement (DPA) and answers to security questionnaires are available on request. - VenueX does not connect to the brand's POS, CRM, ERP or other production systems. - Store sales go only to the ad accounts the brand approves. The accounts stay owned by the brand, and VenueX works through partner or OAuth access. - Access inside VenueX is role-based, and each brand's data is isolated from other brands. - Details: https://venuex.io/security ## Not supported - Not supported: a net or incremental store impact number. VenueX does not run holdout or lift tests. - Not supported: results at ad set or ad level. Reporting is at campaign level. - Not supported: budget recommendations, media mix modelling, a split of new and returning customers, or export to BigQuery. - Not supported: store sales uploads to other ad platforms, for example Snap or Yandex. ## Results from public success stories - **Koçtaş** (DIY and home improvement, 263 stores): offline ROAS was 4.6× online ROAS. Store visits grew 112%. https://venuex.io/success-stories/koctas - **Boyner** (department stores, 126 stores): offline ROAS was 3× online ROAS. https://venuex.io/success-stories/boyner - **Karaca** (homeware): omnichannel ROAS was 40% higher when store sales were included. https://venuex.io/success-stories/karaca Each result comes from that client's own study. Periods and methods differ. ## Frequently asked questions ### Would these shoppers have come to the store anyway? Some would. The ad platforms report store sales from people their ads reached. That links store sales to campaigns, but it does not prove that the ad caused each sale. ### How much work is it for our team? The brand sends a daily sales file and gives access to its ad accounts. VenueX runs the checks, uploads and error fixes. ### Can the ad platforms use store sales for bidding? Where the platform allows it, yes. Campaigns can then optimize for store revenue as well as online sales, as in the Koçtaş and Karaca projects. Bidding settings stay with the brand and its agency. ### Do we need to change our agency? No. VenueX uploads store sales into the brand's own ad accounts, and the agency keeps running the campaigns. At Koçtaş, VenueX worked together with the brand's agency partner. ### How is it priced? Pricing is set per customer by the modules used and the number of stores. There is no setup fee. ## Definitions - **Offline conversion:** a store sale uploaded to an ad platform, so the platform can link it to ad interactions. - **Offline ROAS:** store revenue that an ad platform links to a campaign, divided by that campaign's ad spend. - **Online ROAS:** online revenue that the platform links to a campaign, divided by the same ad spend. - **SHA-256 hashing:** a one-way function that turns an email address, phone number or name into a fixed code. The platform compares codes, so the raw value is not sent. ## Related pages - Platform overview: https://venuex.io/platform - Store presence, store details on Google, Apple Maps, Meta and Yandex: https://venuex.io/platform/store-presence - Local inventory, store stock on Google and Meta: https://venuex.io/platform/local-inventory - Customer feedback, Google review replies: https://venuex.io/platform/reviews - VenueX AI (Beta), questions about stores, reviews and campaign-level ad results: https://venuex.io/platform/venuex-ai - Security and data privacy: https://venuex.io/security - All success stories: https://venuex.io/success-stories ## How to start - Plan a call: a 30-minute intro call about the store network, platforms and the first use case. - See the live demo: the VenueX platform with demo data, https://demo.venuex.io. - Request a store audit: a one-page check of the brand's store profiles and reviews. All three: https://venuex.io/contact. Email: info@venuex.io. VenueX replies within 1 business day.