A step-by-step operating system for dealership organic social content and bounded paid Meta planning, with permissions, routing, and evidence controls.
Social media for car dealerships needs an operating system, not a universal posting schedule or a promise about sales. For an independent or used-car dealer, the central work is making accurate, permissioned dealership information available to buyers while routing every response to a team that can handle it.
This guide separates two lanes that are often mixed together: organic dealership publishing and a bounded paid Meta test. An organic post, boosted post, paid campaign, inventory or catalog unit, Marketplace surface, direct message, call click, form, and qualified sales enquiry are different objects. They need different owners, records, and review rules.
Use this tutorial with the dealership's current licensing, permit, bonding, advertising, price, finance, privacy, consent, intellectual-property, and platform-policy review processes. It is not legal, finance, or platform-eligibility advice. For the broader dealership proposition, see theStacc for auto dealers; this page stays focused on social operations.
Define the dealership jobs and inventory you can represent truthfully
Start with the dealership jobs you can document accurately, then give each job a content owner, source of truth, disclosure reviewer, and next stage. This prevents a social post from implying that a vehicle, price, finance term, person, or offer is available when the dealership cannot support that representation.
Build a job/content boundary before choosing a platform or assigning a creator. In-stock vehicle purchase is not the same job as locate or order, trade-in, finance, service, parts or body shop, community activity, employment, vendor communication, wholesale, or a customer delivery. A person looking for a repair appointment should not be sent through the same route as a buyer asking whether a specific unit remains available.
| Job or content | Proof or permission | Dependency and owner | Gate and next stage |
|---|---|---|---|
| In-stock sale or locate/order | Current vehicle/status source | Inventory source; sales owner | Disclosure review; sales enquiry |
| Trade-in or finance education | Approved educational copy | Department input; finance owner | Current review; appraisal or finance route |
| Service, parts, or body shop | Accurate service scope | Department availability; service owner | Service review; service booking path |
| Community, employment, vendor, wholesale | Event or role approval | Relevant department; named owner | Rights/policy check; appropriate contact path |
| Customer delivery | Written identifiable-media permission | Customer and vehicle record; content owner | Consent/disclosure check; documented use |
For each item, record location, inventory age or refresh time, season, local competitive density, dealership-supplied economics where relevant, staff/on-camera capacity, and the unavailable-stock rule. Name the person responsible for price and disclosure review, and the owner of licensing, permit, bonding, or compliance review. Do not use stock imagery as if it shows dealership inventory, and do not use identifiable people without a documented permission record.
Make the status source usable by the person publishing: note when it was checked, who can correct it, and what happens if an item is removed, reserved, or cannot be discussed. The same discipline applies to a trade-in question, a service offer, an employment post, or a vendor request. A social operator needs a recorded handoff, not an assumption that another department will see a reply.
Separate organic publishing from paid Meta acquisition
Organic publishing and paid Meta acquisition are separate operating lanes: they have different access, spend, audiences, inventory dependencies, approvals, routing, and evidence. Keeping them separate lets a dealer evaluate a scheduled post or a paid test against its own declared purpose instead of blending unlike activity.
Organic publishing is a planned library of approved dealership information. Paid Meta acquisition is a direct-spend activity governed by its account, current official Meta rules, buyer-job scope, and evidence plan. Neither is inherently preferable; the correct choice depends on the dealership's available proof, response coverage, and ability to review a separate cohort.
| Control | Organic publishing | Paid Meta acquisition |
|---|---|---|
| Purpose and owner | Approved dealership information; organic owner | Declared test; paid-social owner |
| Spend and audience | No media spend; publishing audience | Direct-spend cap; defined eligible audience |
| Inventory and creative | Current approved proof and rights | Applicable inventory source, rights, and current Meta review |
| Approval and landing path | Content and department approval | Account approval, landing parity, and routing review |
| Earliest valid stage | Documented response or enquiry | Documented response or enquiry in paid cohort |
| Measurement and stop | Organic source records; content pause owner | Billing and CRM/DMS reconciliation; campaign pause owner |
theStacc’s Social Media module supports scheduled organic posts and approval flows across Instagram, LinkedIn, X, and Facebook. It does not operate paid Meta campaigns, automotive feeds, Marketplace listings, a DMS or CRM, finance, or compliance workflows. Keep access and approvals clear before asking anyone to publish.
Document the account owner and access boundary for each lane. A team should be able to identify who may approve an organic asset, who owns a direct-spend decision, which content is available for reuse, and who stops work when a record is no longer current. This is particularly important where the same vehicle photo or delivery media could otherwise move between an organic post and a paid activity without a new review.
Need help establishing the organic publishing workflow and approval path?
Choose content from buyer questions and dealership proof
Choose social content from questions the dealership can answer with current, permissioned proof. A walkaround, process explanation, ownership tip, community item, or delivery story is usable only when its vehicle status, people, claims, rights, and disclosures have been checked for the intended platform and use.
A useful content plan begins with the buyer question and the dealership proof behind it, not a calendar quota. Inventory walkarounds can answer vehicle-specific questions when status is current. Staff and process explanations can clarify how the dealership handles an appraisal, service visit, or vehicle handover when the responsible department approves the explanation.
- Accurate inventory walkarounds: identify the source and current status; define the unavailable-stock alternative before publishing.
- Staff and process explanations: use employees who have given written permission and content approved by the department owner.
- Trade-in or finance education: keep it general, reviewed by the relevant owner, and separate from individual terms or promises.
- Service and ownership education: route service, parts, and body-shop questions to their own department rather than sales by default.
- Community activity and delivery stories: record rights, consent, approved platforms, expiry, revocation owner, and storage location.
Use a permission and proof register for every reusable asset: asset, person, and vehicle; source; rights or consent record; claim and disclosure review; approved platforms and uses; start and expiry date; revocation owner; and storage location. If the register does not support a post, use a different source rather than filling the gap with an invented testimonial, generic “customer story,” or unverified promotion.
Reviews need the same restraint. Google says review content should reflect genuine experiences and prohibits incentives in exchange for reviews; its public-reply guidance also calls for care with private information. The FTC's consumer-reviews rule is a federal baseline, not a substitute for current state or dealer-specific review. See the Local SEO module for the product's GBP-post and review-reply workflow boundaries.
Approval should include the exact intended use, not merely a general permission to take a photo. A delivery image approved for a dealership archive may not be approved for an organic post or a paid creative. Keep the record linked to the asset, and give the revocation owner a practical way to remove or retire it. When the needed permission or proof is unavailable, publish a different, supportable item.
Gate paid inventory or lead work through current official requirements
A paid inventory or lead test should not start from a boosted organic post. Before any paid work, the dealer needs current official Meta documentation, authorised account and Page access, ownership of any applicable inventory source, reviewed landing content, staffed routing, tested measurement, and a named pause owner.
Meta's official automotive materials are the reference point for named automotive surfaces, including Automotive Inventory Ads. Do not infer availability from another dealership, a vendor article, or an old account setup. Meta access and product availability can be account-, region-, and policy-dependent; verify the current official documentation for the exact account before planning an inventory or lead activity.
- Confirm authorised account and Page access, named owners, and the current official Meta documentation.
- Where applicable, confirm who owns the inventory, catalog, or feed source and who pauses it when vehicle status becomes unreliable.
- Check landing-page parity, claim and disclosure review, media permissions, geography, and the department that can handle the stated buyer job.
- Set a direct-spend cap, BDC coverage, appointment/appraisal/finance capacity ceiling, tracking test, and feed or campaign pause owner.
The federal Used Car Rule is a baseline for covered dealer Buyers Guide disclosures; it does not approve individual social-ad copy, price statements, promotions, or finance claims. Current jurisdiction and dealership review remains necessary. Never treat a Meta tool name, a previous setup, or a platform surface as approval to make a vehicle or finance representation.
Keep a dated check of the official Meta source used for the proposed activity. If the documentation does not settle a question for the dealership account or region, mark the feature or surface unavailable for planning until the appropriate owner verifies it. This avoids presenting an account-specific eligibility decision as a general rule, and it lets the pause owner act when an inventory or landing record changes.
Route every response by dealership intent
Treat every response as an intent record, not a social metric. A comment, direct message, call click, and form can begin a different path; each needs a source identifier, consent handling, vehicle or job type, department owner, duplicate rule, unavailable-stock alternative, and timestamp before it can support a later conclusion.
Define a shared intent-routing matrix before content goes live. The matrix keeps social operators from improvising a response path and gives BDC, sales, service, and finance teams a usable handoff record. It also distinguishes a raw contact signal from an enquiry that meets the dealership's written qualification rule.
| Entry point | Record before handoff | Route and safeguard |
|---|---|---|
| Comment | Content identifier, vehicle/job type, timestamp | Named department; avoid public private-data disclosure |
| Direct message | Consent, geography, contact record, source | Owner and suppression record; unavailable-stock path |
| Call click | Source/content identifier, timing, department | Connected-call rule; duplicate handling and escalation |
| Form | Consent, job type, contactability, source | Qualification rule, owner, and CRM/DMS record |
Write the funnel dictionary in the same system: impression, click, call click, form, connected enquiry, qualified enquiry, booked job, kept appointment, completed job, and completed vehicle sale. For every stage, specify the exact business rule, source system, owner, timestamp, and exclusions. Google Analytics 4 lists recommended lead-generation events, but the dealership must define its own stage rules and reconcile them with CRM or DMS records.
Exclusions matter: employment, vendor, duplicate, wrong-department, wrong-geography, spam, unavailable-inventory, and suppression cases must not silently become qualified enquiries. Keep service jobs separate from sales, and retain cancellations as their own documented state instead of relabelling them.
Use a suppression record whenever a contact has a request or status that affects further communication, and make the escalation route clear for a complaint, privacy issue, or uncertain claim. The operator should be able to see who owns the next action, not just that a platform notification occurred. This is what allows a later appointment or completed transaction to be reconciled without guessing about the original social activity.
Run one bounded organic or paid experiment
Run one bounded organic or paid experiment at a time, with a written cohort and a decision rule before publishing or spending. That scope protects the team from crediting a seasonal change, another channel, unavailable inventory, or unstaffed capacity to a social activity it did not cause.
Create a 28-day experiment sheet that declares whether the activity is organic or paid. Do not combine the two in one result. State the hypothesis in operational terms, then choose a single location, buyer job, content or inventory cohort, and geography that the assigned team can support.
| 28-day experiment field | What to record |
|---|---|
| Scope | Organic or paid flag, hypothesis, location/geography, buyer job, content or inventory cohort |
| Time and capacity | Start/end dates, time or direct-spend cap, BDC and appointment capacity ceiling |
| Controls | Permissions/compliance gate, source identifiers, stage events, exclusions, named owner |
| Review | Evidence lag, review date, and prewritten keep/change/stop rule |
For organic work, the content response-rate formula is: unique attributable comments, DMs, connected calls, or submitted forms meeting the written response rule divided by eligible organic content impressions for scoped posts with a consistent impression definition. Use the declared 28-day organic-post cohort, platform insights plus call/form analytics, an organic-social owner, and exclude paid impressions, staff/admin activity, spam, and duplicates. Mark the measure unavailable when impression definitions cannot be reconciled.
For a paid cohort, keep direct media spend, billing record, CRM/DMS evidence, controller or sales sign-off, and closeout lag separate. The Content SEO module researches, drafts, and queues content; it is not an attribution system for a paid Meta experiment.
Before launch, write the evidence lag as well as the review date. A sale or service completion may appear later than the social response, so an early snapshot cannot close the cohort by itself. Give the owner a prewritten keep, change, or stop rule that addresses the observed stage evidence and the documented capacity ceiling. Do not rewrite the rule after seeing a platform total.
Want to establish the content and approval side before running a bounded test?
Review qualified and completed-outcome evidence
Review social work against qualified and completed-outcome evidence, not reach, engagement, clicks, call clicks, or form totals alone. The review should reconcile source records with inventory, BDC, appointment, and deal-closeout records, then identify mismatches, duplicates, consent gaps, and unstaffed responses before a keep, change, or stop decision.
At the scheduled review, inspect the cohort record rather than reporting a platform dashboard in isolation. Check inventory mismatches, irrelevant job-seeker or vendor responses, duplicates, consent gaps, unstaffed messages or calls, unreachable enquiries, unkept appointments, and unattributed sales. These are operational findings, not noise to remove from a presentation.
The qualified-enquiry rate is unique connected enquiries satisfying written inventory/job, geography, timing, capacity, and contactability rules divided by all unique attributable connected enquiries from the scoped organic or paid cohort. Use separate declared 28-day windows, platform/call/form source plus CRM/BDC records, a BDC or sales-operations owner, and exclude spam, duplicates, employment, vendors, wrong department or geography, and unsupported or unavailable inventory.
The booked-job rate is unique qualified enquiries with a confirmed scheduled appointment mapped to “booked job” divided by all unique qualified enquiries created in that cohort. Use a 28-day enquiry cohort plus declared scheduling lag, the CRM/DMS appointment record, and a BDC or sales-manager owner. Count reschedules once; retain cancellations as booked but not kept; keep service separate from sales.
For paid work, cost per completed vehicle sale is direct attributable paid-Meta media spend divided by unique attributable completed vehicle-sale transactions. Use the declared 28-day paid cohort plus stated sales-cycle/closeout lag, Meta billing and CRM/DMS with deal closeout, and paid-social owner with controller/sales sign-off. Exclude organic labor unless explicitly costed, taxes/fees, deposits, reversals, service jobs, and unattributable sales. Keep, change, or stop from this declared evidence—not an engagement total.
Keep the evidence and exclusions visible to the people who own content, paid activity, BDC handling, and sales operations. If a later record cannot be connected to the declared cohort, label it unattributable instead of assigning it to social. This preserves the distinction between an activity that generated an early response and one that can be reconciled through the dealership's own completed-outcome records.
FAQ
These answers keep the operating boundaries clear: platform selection, cadence, and budget are dealership-specific decisions, while official Meta requirements must be checked for the account and region in question. A valid review connects documented content or paid cohorts to staffed routing and later business records without collapsing every response into a sale.
Use the platforms where the dealership can maintain accurate, permissioned content and staff the resulting responses. Choose by buyer job, local market, available inventory or department proof, account access, and routing capacity—not a universal platform ranking. Review platform rules and the dealership's policy requirements before publishing.
Post only material the dealership can substantiate: current walkarounds, staff or process explanations, trade-in and finance education reviewed by the appropriate owner, service or ownership education, community activity, and permissioned delivery stories. Record the vehicle status, media rights, disclosure review, intended use, and removal owner for each asset.
There is no universal posting cadence. Set a schedule only after the dealership confirms inventory refresh timing, staff availability, content approval capacity, response coverage, and the ability to keep claims current. A smaller documented plan is preferable to publishing material that cannot be reviewed, routed, or corrected.
They solve different jobs. Organic publishing can maintain an approved library of dealership content; a paid Meta test has separate spend, access, audience, measurement, and pause controls. Use either or both only when each lane has its own owner, evidence plan, compliance review, and response capacity.
Meta describes Automotive Inventory Ads in its official automotive documentation. Availability, setup, and eligibility can vary by account, region, and current policy, so a dealership should verify the current Meta requirements and any applicable inventory-source obligations before treating the format as available for its account.
There is no universal daily budget. Set any direct-spend cap from the dealership's stated economics, inventory or buyer-job cohort, geography, BDC coverage, appointment capacity, measurement plan, and stop rule. A cap without those inputs cannot establish whether a paid test is appropriate or conclusive.
Marketplace availability and behaviour are account-, region-, and policy-dependent. Verify the current official Meta documentation for the specific dealership account before publishing or planning around that surface. Do not assume that an inventory item, listing method, or response path available elsewhere is available to the dealership.
Define source and stage rules before the cohort starts, then reconcile attributable paid or organic records with CRM or DMS, appointment, and deal-closeout records. A completed vehicle sale is a later business event; impressions, clicks, call clicks, and forms are not substitutes for a documented completed-sale record.
Build the operating system before publishing or spending
A dealership social programme is ready to proceed only when its content truth, permissions, disclosures, routing, capacity, measurement, and pause controls are documented. This approach does not predict a platform outcome; it gives the dealer a way to decide what to publish, what to test, and what evidence is required to keep, change, or stop.
Keep organic publishing separate from paid Meta acquisition, and treat either as one part of a broader dealership plan. For organic-search work, see the automotive SEO guide. Establish the relevant owners before publishing, especially when an item refers to current inventory, people, reviews, finance, promotions, or a customer experience.
Use a documented social workflow that preserves the boundaries in this guide.
Sources & references
Researched, written, and published articles that compound organic traffic.