Your DAM, your CRM, the systems your locations run on, your data warehouse, your identity provider, your accounting system and every media platform your dealers buy from. Defined integrations with a written scope, a development environment, your sign-off, and a log you can see.
A co-op program touches the DAM, the CRM, the sales feed, the identity provider, the media platforms and the general ledger. Every one of those connections is a defined integration in Co-Op Command, not a spreadsheet handoff. What follows is what we connect to today and how each one behaves.
Approved assets flow from your DAM into the Co-Op Command asset library through the DAM’s API, with your metadata and permissions intact. The DAM stays the system of record; the portal always shows the current approved version.
Leads, campaign activity and co-op spend are pushed to your CRM; account, territory and ownership data come back to keep the dealer roster and balances current. Standard objects out of the box, custom objects mapped at setup.
Job, lead and customer events from the systems your locations already run in can trigger local marketing: a job started, a job completed, a review request. Each location sees only its own data.
A scheduled feed of every order, claim, fund movement and media result lands in your warehouse in your schema, so your BI team can join co-op to sales, service and finance data without asking us for an export.
Accruals are calculated from your sales or purchase data by dealer, brand and product line. We take a file, a feed or a system connection, on the cadence you choose, and post balances as the data arrives.
SAML or OIDC single sign-on against your identity provider, with dealer and corporate roles mapped from your directory. Sites and users load from your store list and are re-synced on your schedule.
Reimbursements run weekly by ACH to each dealer’s bank on file. Payment, remittance and fund-liability data are structured for your accounting system and reconcile line by line to approved, proven transactions.
Google, Microsoft, Meta, LinkedIn, TikTok, streaming and programmatic partners report results back to the order that paid for them. Call tracking numbers and landing pages tie phone calls and form fills to the campaign and the location.
Everything the portal can do, your systems can do: read balances, create and check claims, pull reports, push assets. Documented REST endpoints with per-client keys.
Every report as a file your GL, CRM, dealer portal or warehouse can import as-is: your layout, field names and codes, delivered by SFTP, email, feed or API on your schedule, with transaction IDs for reconciliation. How custom exports work →
We confirm which objects move in which direction, who owns each field, and what “done” looks like, and document it as a written scope with a fee, a schedule and acceptance criteria before any build starts.
The integration is built and tested against your sandbox or a copy of your data, never against production first.
Your team tests with real cases. Nothing moves to production until you confirm it.
Every sync is logged. Failures alert us before they alert you, and your account team sees the same log you do.
| The other administrators still the industry standard | Co-Op Command |
|---|---|
| Program data lives inside the administrator’s system. Getting it out is a project, or a request that goes unanswered. | Every table is exportable from the portal, on a schedule to your warehouse, or through the API. No request needed. |
| Reports arrive as PDFs at month end. | Reports are live views of the same rows your warehouse receives, and custom reports are built with you during setup. |
| Switching administrators means rebuilding history. | History exports in full on the day you leave, with every claim, payment and proof attached. |
A program review includes an integration map: which of your systems feed the program, which receive from it, and what each connection takes to build.