Rules-enforced execution. Before campaigns go live.
Campaign blueprints, pre-launch QA and tracking readiness run as rules. Every check has a defined pass/fail and a full audit trail. One taxonomy, one UTM schema. That is how ACE matches a campaign to a conversion.
Six execution-standard systems.
The standard, written down.
The naming convention, as enforced
Every campaign identifier decomposes into four segments. A name that does not decompose fails the blueprint check before a specialist opens a platform.
The UTM schema, as validated
Five parameters. The first four are required on every paid link. This is the join key ACE uses to match a campaign to a conversion.
The audit log, as written
Actor, timestamp, rule reference, outcome. Machine checks and human overrides land in the same log.
NRT-EMEA-Q2-PROSPECT · launch gate.
Campaign-launch checklist as it appears in Adeqo. Critical and warning items must be resolved or explicitly overridden before the gate opens.
Tracking readiness, scored.
A failing check here invalidates every number downstream of it.
Example · open issues across the account.
Every fix writes back to the knowledge graph ACE maintains.
What the rules buy you.
Attribution that resolves
One taxonomy and one UTM schema across the ad accounts and the CRM, so a conversion resolves to the campaign that produced it. When source capture breaks, reconciliation raises it with a severity and a named owner.
Launch control
A campaign does not go live until its checks pass, or until an override is signed off and written to the log.
A reviewable record
Every check, override and decision lands in one log with actor, timestamp, rule reference and outcome. Machine checks and human overrides go to the same place.