Define the source of truth separately for campaign spend, creative assets, customer approvals and commercial billing. Exchange stable references and selected approved measures rather than assuming every platform metric belongs in the ERP. A campaign activation event should not automatically establish that all creative deliverables were accepted or that a client charge is authorized.
Understand the decision
Advertising platforms, creative repositories and project tools can report different dates and identifiers for the same campaign. Time zones, credits and later adjustments can change reported spend. The integration should expose those differences and retain the reporting basis rather than silently rewriting previously reviewed commercial records.
Work through the requirements
- Assign ownership for spend and approval data.
- Map campaign and asset identifiers.
- Review adjustments against the reporting basis.
| Record or decision | Why it matters |
|---|---|
| Platform mapping | Connects campaign references across systems. |
| Spend reconciliation | Explains adjustments and reporting periods. |
| Approval evidence | Separates asset acceptance from campaign activation. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
A connector that transfers numbers does not make those numbers comparable. Preserve time period, currency and adjustment rules, and separate campaign performance reporting from the evidence used to authorize project completion or customer billing.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Marketing agencies in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗Odoo 19: sales quotations and invoicing methods ↗