How do you audit automated changes to ecommerce creative?

01

Why is platform history not a complete audit trail?

Platform history explains activity inside one system; an audit trail connects the complete change across systems and decisions.

Shopify Flow’s version history can show workflow edits, activations, deactivations, exports, timestamps, and whether a user or Shopify automation made the change. That is useful evidence, but it does not automatically connect a workflow revision to your approved creative file, downstream ad object, reviewer decision, or recovery procedure (Shopify Flow version history).

Execution evidence may also expire sooner than your team expects. Shopify says completed Flow runs are retained for 14 days. Runs can be searched using details such as run ID, workflow, trigger, time, errors, and resource data. Export or copy the evidence your team needs before it disappears (Shopify workflow runs).

Your internal record should therefore act as an index rather than duplicate every platform log. It should tell a reviewer which source was approved, which automation acted on it, what output appeared, who accepted or rejected that output, and where the supporting platform evidence is stored.

02

Which changes deserve their own event record?

Record any automated event that changes what customers see, where an item is routed, which product an asset represents, or whether approved material is altered.

Create an event when an automation changes a product tag, status, destination, collection, offer, landing page, audience-facing claim, image, video, audio, crop, CTA, or publishing state. Also record failed and retried executions when they could create duplicate work or an uncertain final state.

Do not log every harmless background operation. Use a materiality rule: would a creative operator, approver, customer-support lead, compliance reviewer, or media buyer need this fact to explain the resulting output? If yes, preserve it.

A useful event model follows six questions: what happened, when did it happen, where did it happen, what initiated it, what was the outcome, and which person or system was responsible. Those elements align with the general audit-record attributes described in NIST guidance (NIST audit-record guidance).

03

How should you identify products, assets, and workflows?

Assign durable internal IDs and retain the platform IDs needed to reconcile the same object across systems.

Names are labels, not reliable join keys. A product title, campaign name, SKU, or filename can be edited or reused. Record the Shopify product and variant IDs, internal creative ID, workflow ID and version, platform campaign or ad ID, and resulting asset ID where each is available. Shopify GraphQL global IDs uniquely identify API objects, making them stronger reconciliation keys than names alone (Shopify global IDs).

Use a consistent internal format such as CREATIVE-1042-v3 for the approved asset and EVT-2026-00417 for a change. A parent_event_id should connect a downstream action to the event that initiated the handoff.

For files, retain the source filename, storage location, version, and checksum. A checksum is a file-derived value that helps distinguish two files even when they have similar names. Keep the source itself in controlled storage rather than relying on a platform preview.

04

What should the approved source record contain?

The source record should capture exactly what the team approved before any automation or platform transformation occurred.

Record the internal creative ID and version, product and variant IDs, source file, checksum, storage URL, approved copy, offer, CTA, claims, destination URL, approver, and approval time. If an approval has conditions—such as a required disclaimer or prohibited crop—write those conditions as structured notes rather than leaving them in chat.

For a product-routing change, capture the relevant pre-change tags, status, collection, destination, or other state. For creative, save a viewable preview alongside the original file. The purpose is to make the question “What entered the automation?” answerable without reconstructing it from memory.

Freeze the source version once it is approved. A later copy correction or resized source should receive a new version, even if the team considers it a minor update. Otherwise, the audit trail can point to a file that no longer matches what originally ran.

05

How do you record an automation definition and execution?

Keep the reusable automation configuration separate from each time that automation runs.

The definition record describes the system and account, workflow or rule ID, version, trigger, conditions, actions, selected transformation settings, owner, activation time, and a screenshot or exported configuration. The execution record describes one occurrence: event ID, run or change-log ID, UTC timestamp, triggering object, actor, before state, action, after state, outcome, errors, and retries.

Shopify Flow’s Get workflow run data action can expose identifiers, retry information, UTC start time, and the triggering event. Its Log output action can write selected values into the run log. Use that capability to preserve your internal creative ID, launch code, or another business-specific key when the default log does not contain the context needed for reconciliation (Get workflow run data; Log output).

Distinguish the actor precisely: named user, installed app, scheduled workflow, platform automation, or API process. “System” is too vague when several automations can act on the same object.

06

How should platform-modified creative be documented?

Save both the submitted source and the platform-produced result, together with the settings that explain the difference.

TikTok’s Automate Creative can apply changes such as resizing, resolution enhancement, music replacement, and audio effects. The advertiser selects enabled features during setup. Record those selections and save the setup preview before publication (TikTok Automate Creative).

TikTok states that Automate Creative settings cannot be changed after publication; using different settings requires a new campaign. That makes the pre-publication configuration and preview part of the approval evidence, not optional setup notes (TikTok Automate Creative).

After publication, record the resulting campaign, ad-group, ad, and asset IDs where applicable; publication time; observed differences; reviewer; and disposition. TikTok Ads Manager change logs can provide supporting details including time, object name, object type, object ID, activity details, and operator (TikTok change logs).

07

What is the minimum viable change log?

A single spreadsheet or database table can provide a useful audit trail if every event receives a unique ID and links to its source evidence.

Do not wait for a custom data warehouse. Begin with one row per event and define who fills in each field. Use controlled values for outcomes such as completed, failed, retried, rejected, and rolled_back. Store long screenshots, files, and exports elsewhere, then link to them from the log.

The log should be append-oriented: correct mistakes with an amended record or documented update rather than silently replacing historical values. Restrict editing where practical, and identify a primary owner plus a backup owner for exports and reviews.

1. change_event_id: your unique internal event key.
2. parent_event_id: the initiating or preceding event.
3. occurred_at_utc: one comparable timestamp across systems.
4. system_account: the platform and relevant account.
5. object_type and object_id: the product, variant, workflow, campaign, ad, or asset.
6. source_id and source_version: the approved input.
7. automation_id and automation_version: the responsible rule or workflow.
8. trigger_or_actor: the person, app, schedule, event, or platform automation.
9. before_state: the relevant previous value or asset.
10. settings_or_action: the routing instruction or transformation configuration.
11. after_state and output_id: the resulting value, object, or asset.
12. outcome: completed, failed, retried, rejected, or rolled back.
13. approval_or_exception: the decision, owner, reason, and timestamp.
14. rollback_instructions: the exact recovery procedure and responsible owner.
15. evidence_link: the source file, export, screenshot, preview, or platform log.

08

What does a Shopify Flow–to–modified-asset handoff look like?

Treat the Shopify event, the cross-system handoff, and the platform transformation as separate events linked by parent IDs.

This example does not imply that Shopify Flow directly publishes to TikTok. It shows how a team can preserve continuity when a Shopify event prompts a separate operator or process to prepare and publish creative in an ad platform.

The final record should let a reviewer begin with the approved source and follow the chain to the published output without relying on campaign names, Slack history, or one person’s memory.

1. Approve CREATIVE-1042-v3. Record its checksum, storage URL, Shopify product and variant IDs, approved copy, landing page, approver, and approval time.
2. Record the Shopify Flow definition. For example: workflow version 18 detects a launch condition and applies a routing tag or sends a downstream notification. Save its workflow ID, trigger, conditions, actions, activation time, owner, and configuration evidence.
3. Capture the Flow execution. Record the run ID, UTC start time, triggering product IDs, action result, retries, and errors. Log CREATIVE-1042-v3 or a launch code if that key is needed to connect the run to creative operations.
4. Create a separate handoff event. Record the operator or process that used CREATIVE-1042-v3, the time of the handoff, and the resulting TikTok campaign, ad-group, and ad IDs. Link this event to the Flow event using parent_event_id.
5. Before publication, record that Automate Creative was enabled, list every selected option, and save the configuration screenshot and preview. Do not describe the result merely as “TikTok optimized.”
6. After publication, save the resulting ad ID and preview, observed visual or audio changes, reviewer, decision, operator, and publication time. Link supporting TikTok change-log evidence.
7. Define rollback explicitly. It might mean pausing the ad and returning to the approved source. If different Automate Creative settings are required, TikTok says a new campaign must be created. Record who makes that decision and who performs it.

09

Who owns reviews, exceptions, and rollback?

Assign one operational owner for record completeness and one decision owner for approving exceptions or initiating rollback.

The operational owner checks missing IDs, evidence links, exports, and timestamps. The decision owner determines whether a transformed output remains acceptable. For higher-risk claims, offers, or product changes, identify any additional approver before automation is enabled.

Review short-lived records frequently enough to export them before platform retention windows close. A weekly export is a practical internal cadence for Shopify Flow runs because completed runs are retained for 14 days; conduct a broader monthly review for broken links, orphaned events, inactive workflows, unresolved exceptions, and outdated rollback instructions.

ATIYO can serve as the central creative-context record by organizing roadmaps, briefs, brand context, assets, iterations, and reusable learnings. It does not connect to ad accounts, buy media, calculate ROAS, or automatically know performance. Media performance remains in the ad platform. ATIYO preserves the creative context and learnings that help the team understand what was made, changed, approved, and learned. See Creative Operations Software, How ATIYO Fits Into Your Workflow, and Best Practices for a Healthy Creative Pipeline.