What this checkpoint covers
Zivquorna Conservatories is an invented installer of conservatories and orangeries. Visitors request a design visit, a designer quotes and the sale closes weeks or months later; qualified leads and contracts go back to Google Ads by file. The questions apply the guide to conversion windows and attribution, the tutorial on reconciling Google Ads conversions with sales and the offline conversion upload SOP.
Zivquorna Conservatories: actions, lag and recent events
| Action | Role | Model | Click window in May |
|---|---|---|---|
| Design visit request | Primary | Data-driven | 30 days |
| Sales-qualified lead (uploaded weekly) | Primary | Data-driven | 90 days |
| Signed contract (uploaded weekly) | Secondary | Last click | 90 days |
Days from click to design visit request, from CRM leads with a click identifier: 0 to 7, 58%; 8 to 30, 27%; 31 to 60, 11%; over 60, 4%. Contracts follow the first click by 40 to 150 days. A video campaign's engaged-view conversions are added to the design visit figure the owner reads.
Halfway through June the design visit window was lengthened to 60 days. Over the last three closed months, CRM leads with an identifier ran at 0.83, 0.85 and 0.84 of the platform's design visit requests. Last Monday, 52 qualified leads were exported, 5 removed for consent, 47 uploaded and all 47 rejected for an unknown action name; a clean-up had renamed the action in the account.
Task
- Commit to an answer and the reason behind it for each scenario; a right answer for the wrong reason counts as a miss.
- For each miss, reopen the section the explanation links.
Questions
- The agency wants last click on every action "so the numbers are simple". Customers often search for orangery ideas first and the brand name weeks later. What do you set?
- The marketing manager wants every window, video included, at the longest available "so nothing is missed". What should decide each window?
- June looks far better than May in the standard columns, and finance wants June compared with the CRM. How is June read?
- A week after month end, finance asks for a reconciliation of the month from daily totals. What do you change?
- The managing director tells the agency to make Google Ads match the CRM exactly. What do you say?
- Sales proposes uploading every lead stage from its own spreadsheet, including leads with no consent value recorded. Which outcomes go, from where, and which records stop?
- Paid media sees qualified leads collapse last week and wants bidding moved back to design visit requests. What happens?
Answers explained
- A model per action, by its use. Last click hands all credit to the brand click, so generic campaigns lose credit and bidding follows it. The two primary actions feed the same campaigns and share data-driven; the contract, a secondary action checked against the CRM, can stay on last click. Settle it once. See choosing a model for each action.
- The business's own lag. The old click window missed every request arriving after a month; the June window holds the bulk, and stretching further credits requests that owe the ads little. The contract tail belongs to Offline Conversion ImportUploading outcomes recorded outside the website, such as closed deals, to an ad platform.. Engaged-view conversions leave the main figure for their own line, with their Lookback WindowThe time after an ad interaction in which a conversion can still be credited to it. stated. See setting windows from your own lag.
- As a break in the series, not an improvement. Standard columns place conversions on the click date, so June mixes two windows and its late days are still filling in. Compare a month wholly under the new window with one under the old, each read after its window closed, and use conversion time for the CRM comparison. Reset the target on the new basis. See reporting by click date and by conversion time.
- A closed period, by identifier. Reconcile a month whose longest click window on the primary actions has closed, exported by conversion time, and match leads by the stored click identifier, falling back to daily totals only where none exists. Record the settings in force. See the reconciliation steps.
- They will never match; the ratio is the target. The platform counts view-based, modelled and cross-device conversions the CRM cannot tie to a click; the CRM knows which leads were duplicates or junk and holds leads after the window. Zivquorna's ratio holds steady, so the gap is structure, and targets are converted through it. See calculating the ratio and its trend.
- The outcomes the plan names, from the CRM, with consent. The written list decides which stages feed which action: the Sales-Qualified LeadA lead that sales has reviewed and accepted as a genuine opportunity to pursue. with its exit criteria, and contracts with value. Export from the CRM by stage-change time, never a side spreadsheet. A missing consent value counts as a no. See the upload procedure.
- Fix the upload, not the bidding. Every row was rejected for the action name, so the list and the account have drifted apart: realign them through the plan, upload the records never accepted, log it and tell paid media the week is understated. Conversion LagThe time between an ad interaction and the conversion it leads to, which leaves the most recent reporting days incomplete. already thins recent weeks; switching goals would restart learning on an artefact. See reading results and fixing rejected rows.
Where to go next
If the settings, the split month or the reconciliation tripped you up, work through the piano retailer reconciliation exercise again. Misses on the two upload questions at the end go back to the offline conversion upload SOP, from the outcome list to the record of each upload. The advanced Google Ads level covers the signals these settings count.
