Reading Posting Analytics by Rep and Source

A dashboard full of numbers is not the same as an answer. Plenty of managers have opened a report, seen that Rep A posted 41 units and Rep B posted 17, and walked onto the floor ready to praise one and reprimand the other. Then they learn that Rep B was handed the hard-to-photograph trade-ins and spent two days on the road, while Rep A was working a batch of identical sedans from one auction run. The numbers were accurate. The conclusion was wrong.

Posting analytics are only as useful as the questions you bring to them. PostToMarket gives managers team analytics showing posting activity by rep and source. This article explains how to read that view with discipline: what to compare, what the numbers cannot tell you, and how to turn a table into a coaching conversation and an inventory decision.

It is written for GMs, used-car managers and internet directors who want to use posting analytics by rep and source to manage the work, not to police it. One note on scope: the exact figures available in the Analytics area are best learned by opening it with your own data. What follows is a framework for interpreting activity data in a posting workflow, not a catalog of screens.

What "By Rep" and "By Source" Actually Mean

Two cuts of the same activity answer two different management questions.

By rep: who is doing the work

The by-rep view groups posting activity by the person who did it. It answers questions about the team:

• Who is posting consistently, and who is posting in bursts?
• Is the workload balanced, or is one person carrying most of the posting?
• Do associates, who are assigned units by a manager, keep up with what they were given?
• Are the reps who are strong on the floor also strong at keeping listings current?

By source: where the work came from

The by-source view groups activity by where the posting originated. Depending on how your store works, that can mean how vehicles entered inventory, such as a bulk import, a capture from an auction or wholesale site or a manual entry, and which posting destinations were used. It answers questions about process:

• Which inventory channel produces the most posted units?
• Do units from one source fail more often or sit longer in draft?
• Are certain sources producing the units that your reps actually post, or are they accumulating unposted?

Check the Analytics area to see how sources are grouped for your account, since that is the definition that matters for your store.

Why you need both

A rep view without a source view blames people for process problems. A source view without a rep view hides who is struggling. Look at them together before you act on either.

Setting the Questions Before Opening the Report

Looking at data without a question leads to narratives that fit the first number you notice. Decide what you are trying to learn.

Five useful questions for a weekly review

1. Is every rep with units in a queue actually posting?
2. Are there units that have been in draft or posting for too long?
3. Is the failed count rising, and from which source?
4. Which source supplies the units that move fastest from import to posted?
5. Is posting activity spread through the week or concentrated into a rush?

A conservative, steady pattern is healthier than a burst. The reasons are covered in The Best Posting Schedule for a Dealership Facebook Marketplace Workflow, and the same logic applies to analysis: a flat, steady line is usually a sign of a well-run process.

Pick a comparison window

• Weekly for operations: who is keeping up.
• Monthly for patterns: which sources and reps trend up or down.
• Event-based after a push, a new auction run or a staffing change.

Compare like with like. A holiday week against a normal week will always mislead.

Interpreting the Numbers Without Fooling Yourself

The most important skill in reading analytics is knowing what the numbers do not say.

Volume is not quality

A rep who posts a lot is not necessarily a rep who posts well. Look for evidence beyond count: are the descriptions edited, are the photos chosen with care, are the units priced to compete? Pair posting activity with what happens next, whether inquiries arrive in the leads inbox and whether units move.

Context changes everything

Before you draw conclusions from a difference between reps, check:

• Assigned workload. Did the manager give one associate more complicated units?
• Hours worked. Part-time reps will post less by design.
• Unit mix. Trucks with long option lists take longer to write up than basic commuters.
• Interruptions. A rep who worked a heavy up schedule had less desk time.
• Data quality. A source that produces many failed units may reflect data problems, not rep performance. Import History and Row-Level Error Logs: Fix Bad Rows Before They Post explains how to find the cause upstream.

An illustrative example

Consider a six-person floor over a week. The team posts 90 units in total. One rep accounts for 35, another for 5. At first glance the second rep looks like a problem. On inspection:

• The first rep works the day shift and self-queues from a fresh auction import.
• The second rep covers evenings and weekends, spends most of the time in customer conversations and was assigned a handful of high-effort units that required photo retakes.
• The source view shows that the auction import units flow through the system with few failures, while the manual entries need repairs.

The right management response is not discipline. It is to rebalance the assignments, fix the manual entry process and ask the second rep what slows them down. The same number leads to three different conclusions depending on the context.

From Analytics to Action: A Manager's Routine

Analytics are valuable only if they change a decision.

A 20-minute weekly routine

1. Open the report for the previous seven days.
2. Scan by rep. Note anyone with no activity, anyone with a spike and anyone with a sudden drop.
3. Scan by source. Note which source dominates and which has stalled.
4. Cross-check with the team queue view to see whether stalled units are claimed by someone who is out. Using the Team Queue View to Release and Reassign Claims covers the next step.
5. Pick two actions for the coming week, no more.

Turning findings into actions

Handle the people side carefully

Share the data with reps privately first. Ask for their explanation before you conclude anything. Use the numbers to open a conversation, not close one. A report that is used as a weapon will be gamed within a week, and the numbers will stop meaning anything.

Avoid vanity targets

Do not set a goal like "everyone posts 25 units a day." Posting too fast is a risk in itself, and Facebook's ranking and integrity systems respond to behavior, not to your quotas. Set standards around steadiness, accuracy and ownership, and treat any specific daily cadence as a conservative operating standard you chose, not a rule from Meta.

How PostToMarket Automates This

Analytics are only as reliable as the underlying workflow. PostToMarket makes the workflow consistent enough for the numbers to mean something.

Consistent inputs

• Per-rep queues, so activity is tied to a person instead of a shared login.
• Manager assignment to associate queues and self-queuing for sales reps, so ownership is clear.
• Inventory statuses: draft, posting, posted, sold and failed.
• Bulk CSV and Excel import with import history and row-level error logs, plus capture from auction and wholesale sites.

Consistent pacing

The Chrome extension posts to Facebook Marketplace, and also to your profile and groups, one vehicle at a time with human-like delays. Daily post limits and delays are enforced on the server, so the report reflects steady behavior and not whoever pushed hardest on a given day.

Manager visibility

• Team analytics for posting by rep and source.
• A team queue view to see and release claims.
• A leads inbox for managers, so posting activity can be compared with the inquiries that follow.

PostToMarket is an independent tool, not affiliated with, endorsed by or sponsored by Meta. It does not guarantee reach, leads or sales; analytics show your team's activity, and they do not predict how Facebook will distribute any listing.

See Your Team's Posting Clearly: Start the 10-Day Free Trial

You cannot manage what you cannot see, and you cannot coach what you cannot compare. Posting analytics by rep and source turn scattered effort into a picture a manager can use, as long as you read it with context and a question in mind.

Try the Analytics area and the whole workflow during the 10-day free trial, with secure Stripe checkout and the freedom to cancel anytime. The Starter plan at $59 per month serves a solo seller or independent lot with 1 login. The Dealership plan at $299 per month covers up to 13 team logins and 2 managers, which is where by-rep and by-source analytics become genuinely useful.

Start your 10-day free trial, run a week of real posting and bring a question to the report. Reading posting analytics by rep and source starts with asking better questions of your own team.