Key takeaways
- Every attribution window and conversion definition is a decision with a reason, and that reason must travel with the setting or it becomes invisible.
- Tracking gaps like an untrackable referral flow should be documented as known, time-bounded conditions with explicit triggers for resolution.
- AI tools optimize toward the signal they see with no awareness of whether the conversion definition or window still fits the business.
- Good measurement documentation answers four questions: what is the setting, why was it chosen, what does it miss, and what would change it.
- Undocumented attribution decisions compound over time, turning a temporary trade-off into a permanent misread that scales with the budget.
The number is fine. The context behind it is gone.
Attribution settings are not technical defaults. They are decisions. Someone chose a 7-day click window over a 28-day one. Someone defined a conversion as a form fill rather than a qualified lead. Someone decided not to track a specific event because the engineering lift was too high that quarter. Each of those choices made sense at the time, given the business, the platform, and the trade-offs on the table.
The problem is that the reason rarely travels with the setting. A new hire reads a CPA of $42 and assumes the account is healthy. An AI tool ingests the conversion data and starts optimizing toward it. Neither one knows that the conversion event was redefined six months ago, or that a major traffic source is excluded from the attribution window entirely.
This is not a data quality problem in the traditional sense. The numbers are accurate. The context that makes them interpretable is just missing.
A concrete example: the partner page case
Consider a scenario that comes up often in performance accounts. A team is running paid campaigns and sees CPA drop roughly 40 percent over two quarters. Leadership is pleased. The media buyer knows something the dashboard does not: a new partner referral page went live during that same period, and the conversions it drives are not trackable with the current pixel setup.
The CPA improvement is real in the data. It may or may not be real in the business. The tracked conversions look cheaper because a portion of actual conversions are invisible. The account is being optimized toward a signal that is structurally incomplete, and the deadline to fix the tracking is tied to a product release that keeps slipping.
This is a measurement decision with a deadline and a known gap. It is also exactly the kind of context that never makes it into the ad account, the brief, or the AI tool.
If the media buyer who knows this leaves, the next person inherits a CPA trend that looks like a win and is actually a question mark. If an AI tool is asked to scale the campaigns, it will scale toward the incomplete signal with full confidence.
Why measurement decisions are different from other decisions
Most teams document strategy reasonably well, or at least they try. Measurement decisions get treated differently because they feel technical and permanent. Once a conversion action is set up, it tends to stay set up. The window gets chosen at launch and never revisited. The exclusions accumulate quietly.
The result is that your measurement stack carries the assumptions of whoever built it, whenever they built it, for whatever the business looked like then. Three things that change constantly: the business model, the product, and the team. Three things that rarely update to reflect those changes: the attribution window, the conversion definition, and the documentation of why both were chosen.
This matters more than it used to because AI tools now act on these signals directly. When a workflow automation or an AI agent reads your conversion data, it does not ask whether the conversion definition is still valid. It optimizes toward what it sees. The gap between what is tracked and what is true becomes a gap between what the AI recommends and what the business actually needs.
What to document and how
Good measurement documentation does not require a formal wiki or a dedicated project. It requires three things to be written down for every significant attribution or conversion decision.
The decision itself
What is the current setting? This includes the attribution window (7-day click, 1-day view, data-driven), the conversion event definition (what action counts, on which page, under what conditions), and any known exclusions or gaps in the tracking coverage.
The reason it was made
Why was this the right choice at the time? Common reasons include: the sales cycle length justified a longer window, engineering could not instrument the ideal event before launch, the previous event was inflating volume with low-quality signals, or a platform change forced a migration that introduced a gap.
This is the part that almost never gets written down, and it is the part that matters most when someone new reads the numbers.
The conditions under which it should be revisited
Every measurement decision has a shelf life. Document the trigger for review. For the partner page example, the trigger is explicit: when the product release ships and the pixel can be placed on the referral flow, the conversion data needs to be reconciled and the CPA trend needs to be re-evaluated against the corrected baseline. That is a specific condition, not a vague intention to revisit someday.
Where attribution decisions break down in practice
At handoffs. When an account moves from one media buyer to another, the new person inherits the settings without the reasoning. They will often leave them in place because changing attribution mid-flight feels risky, even when the original rationale no longer applies.
At AI tool onboarding. When a team connects an AI tool to their ad accounts, the tool reads what is there. It has no way to know that the 7-day window was chosen because the business had a 6-day consideration cycle two years ago and the cycle is now 14 days. It will optimize confidently toward a window that no longer fits the customer journey.
At QBRs. Leadership sees a CPA trend and makes resourcing decisions based on it. If the CPA improvement is partly an artifact of a tracking gap rather than genuine efficiency, the resourcing decision is built on a misread. This is not hypothetical. It happens in accounts where measurement decisions were made correctly and then silently became outdated.
When a competitor or product change shifts the funnel. A new competitor, a pricing change, or a product launch can change where in the funnel users drop off. The conversion event that was a reliable proxy for revenue may no longer be. The attribution window that captured most of the consideration period may now miss a significant portion of it. Neither of these updates itself automatically.
A practical documentation format
For each conversion action or attribution setting that materially affects how you read performance, keep a short record in whatever system your team actually uses. A Notion page, a pinned Slack message, a comment in a shared Sheet. The medium matters less than the habit.
The record should answer four questions in plain language:
- What is the current setting?
- Why was it set this way?
- What is it not capturing, and why was that trade-off acceptable?
- What would trigger a change?
For the partner page example, the answer to question three is explicit: conversions from the referral flow are not tracked because the pixel cannot be placed until the product release. The answer to question four is: when that release ships, reconcile the historical CPA data and update the conversion action before making any budget decisions based on the trend.
This takes about ten minutes to write. It saves hours of misinterpretation downstream and prevents an AI tool from scaling toward the wrong signal.
The compounding cost of undocumented measurement
Undocumented attribution decisions do not stay contained. They compound. A conversion definition that was slightly off becomes the baseline for a year of optimization. A tracking gap that was temporary becomes permanent because nobody remembers it was ever a gap. A window that fit the business in 2022 shapes budget allocation in 2025 because nobody ever had a reason to question it.
The cost shows up in three places. First, in misread performance: campaigns that look efficient because they are optimized toward an incomplete signal. Second, in wasted senior time: every new hire, every AI tool, every quarterly review requires someone to re-explain the context that should have been written down. Third, in bad scaling decisions: when leadership or an automated system acts on numbers without knowing their limits, the errors get larger as the budget grows.
Where Almond fits
Almond's Business Context Engine is built specifically for this problem. When a team connects their ad accounts, Slack, meeting notes, and Notion, the engine captures decisions like the partner page tracking gap as they happen, versions them, and keeps them current. When the product release ships and the tracking changes, that update is recorded in context, not just in the platform.
The result is that when an AI workflow or a new team member asks why CPA dropped 40 percent, the answer includes the known gap, the reason it existed, and the date it was resolved. The number does not get misread because the context that makes it interpretable is already there.
If you want to see how this works on a live account, early access is open at almond.ai. Every member gets a detailed 1:1 Meta and Google ad account audit with the CEO, recorded.
Frequently asked questions
- Why does attribution setup documentation matter for paid media teams?
- Attribution settings are decisions made at a point in time for specific business reasons. Without documentation, new hires and AI tools optimize toward signals they cannot fully interpret. A conversion definition that made sense at launch may no longer reflect actual revenue, and the gap compounds silently across every budget decision made against that data.
- What should be documented when you set up conversion tracking?
- Document the setting itself, the reason it was chosen, what it does not capture and why that trade-off was acceptable, and the specific condition that would trigger a change. Four questions, written in plain language, in whatever system the team actually uses. The medium matters less than the habit of recording the reasoning alongside the setting.
- How do attribution window choices affect AI optimization on Meta and Google?
- AI bidding and automation tools optimize toward the conversion signal they see. If the attribution window is misaligned with the actual customer journey, or if a portion of conversions is untracked, the AI scales toward an incomplete signal with full confidence. It has no way to know the window was chosen under different business conditions unless that context is explicitly available.
- What is a tracking gap and how should teams handle it?
- A tracking gap is a portion of conversions that cannot be measured with the current pixel or event setup. Teams should document the gap explicitly: what is not being captured, why the instrumentation is not in place, and what the trigger is for fixing it. Treating a gap as a known, time-bounded condition is far safer than letting it become an invisible assumption in the data.
- How often should attribution settings be reviewed in a performance account?
- At minimum, review attribution settings when the product or pricing changes significantly, when a major traffic source is added or removed, after any platform-forced migration, and at each quarterly business review. The review does not need to result in a change, but the current settings should be confirmed as still valid against the current business model and customer journey.
Almond 2.0 early access
Get a 1:1 Meta and Google audit with the CEO.
Every waitlist member gets a 1:1 audit of their ad accounts. Work email only.