On this page

A link to today’s rebate terms cannot, by itself, explain what a customer saw when they purchased last month. The text may have changed, the page may have displayed a different offer on mobile or the purchase may have followed a partner landing page. A reliable evidence record needs to distinguish the approved promise from the evidence of its presentation.

This is a governance problem before it becomes a storage problem. Decide which questions the records must answer, who is responsible for preserving them and which conclusions require legal review. A technically complete event log is not automatically proof that a customer accepted every term the merchant now wishes to apply.

Identify the promise and acceptance questions evidence must answer

Consider a fictional merchant that changes a purchase reward from $10 to $15 on a planned campaign date. A customer purchases near the transition and later asks why the award was $10. The merchant needs to establish the applicable offer and the evidence available, rather than simply opening the current $15 page.

Separate four questions. What terms were approved for the relevant offer? When was that version intended to apply? What evidence describes the presentation in the customer’s actual purchase path? If the business claims the customer accepted particular terms, what supports that specific claim?

Use an evidence register that does not merge these questions:

Evidence element Fictional entry What it can help establish What it does not establish alone
Approved version OFFER-7, $10 reward Content authorized for publication Actual customer exposure
Effective boundary Defined campaign time and time zone Intended applicability of the version Correct behavior on every page
Presentation record Captured offer placement for the relevant path How the promise was displayed in that context That a specific person read every word
Purchase reference ORDER-74 at a recorded time Relationship to the transaction Agreement to unrelated later changes
Acceptance evidence, if required Actual recorded action and associated wording Facts supporting the claimed acceptance process A universal conclusion of legal enforceability

This distinction is especially useful during a disagreement. It prevents a team from presenting an approval record as if it were an exposure record, or a pageview as if it settled every contractual question.

Define what uncertainty looks like. If the merchant cannot reconstruct a particular presentation, the record should say so. Filling the gap with the current page or a colleague’s memory makes the file look more complete while making its conclusion less reliable.

Preserve the approved version and presentation context

Keep the approved offer text in an intelligible form with its version reference and intended scope. Record the relevant product, audience and time boundary where those affect the promise. A version label is useful only if an authorized reviewer can recover what the version actually contained.

Presentation context may include the placement, language, device layout and purchase path. The fictional transition might have updated the main product page correctly while a cached campaign page still displayed $10. That discrepancy is a fact to investigate, not a reason to assume that every customer received the intended version.

Shopify’s activity-log documentation describes records of administrative actions and their limitations. Such records can help establish that a store change occurred. They should not be treated as a complete archive of a customer’s offer presentation or as a substitute for the specific evidence your approved process requires.

Connect records through stable references rather than collecting unnecessary personal detail. The register should let an authorized reviewer trace an offer version to a relevant purchase and supporting presentation evidence. It should not become an unrestricted folder of customer screenshots, payment credentials and unrelated browsing records.

A difficult case is a translated offer whose meaning differs from the approved source version. Preserve the text actually used in that language and the approval relationship between versions. Recording only the English master would leave an important part of the customer’s context unexplained.

Another difficult case is a purchase completed after the customer saw an earlier invitation. The answer may depend on the disclosed purchase window, the actual terms and the legal assessment of the promise. Preserve the invitation and purchase contexts separately rather than selecting whichever timestamp produces the merchant’s preferred result.

Review record access and retention requirements

Name a custodian for each evidence category and confirm how an authorized person can retrieve it. A record that exists only in an agency employee’s account may become inaccessible when that relationship changes. The governance decision should address continuity before a dispute or program exit makes it urgent.

Determine retention and access requirements from the applicable legal, contractual and privacy review. There is no universal number of months that this article can assign to every merchant and card program. The custodian should know the approved rule, its basis and the event that triggers reassessment.

Test retrieval with the fictional ORDER-74 case. Ask a colleague who did not work on the campaign to recover the approved version, intended time boundary, relevant presentation evidence and any recorded acceptance action. The colleague should also be able to identify missing evidence and the person authorized to interpret it.

Write the review conclusion proportionately. For example: “Records show OFFER-7 was approved for the specified period, but the affected partner placement remains unverified.” That is more honest and useful than calling the file conclusive because it contains several timestamps. The next action should address the actual evidentiary gap.

Keep the evidence process separate from the technical reconstruction described in the evaluation-history article. A system snapshot can establish what an engine calculated from its inputs. This register establishes what records support the customer promise and any claimed agreement. The two may inform the same case while answering different questions.

The finished register should preserve facts without overstating what they prove. When an offer changes, a customer asks a question or a new reviewer joins, the merchant can then explain the relevant history from supported records rather than from today’s page alone.

Discuss the campaign history and records your program needs to support its customer commitments.

Discuss program fit

Source references

Back to contents

General information only

This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.