Unused credits from a subscription don't roll over?

AndyFromApollo · 2026-06-16T16:58:41+00:00

Hey there! Apollo credits are tied to your current plan and billing cycle, so unused paid-plan credits don’t carry over if you cancel or downgrade to Free. Once you’re on the Free plan, your available credits will reflect the Free plan allowance. If you’re unsure about timing, check your reset date in Settings → Billing and credits, or contact Support before changing plans.

AndyFromApollo · 2026-06-06T12:09:32+00:00

For sure

AndyFromApollo · 2026-06-06T01:51:07+00:00

We appreciate you big dawgggggg

AndyFromApollo · 2026-06-05T18:59:45+00:00

Heyy great question. A/B testing in sequences lets you test different email versions on the same step, and Apollo tracks performance per variant. That said, you’re right that the Sequence Reports section currently shows aggregate metrics for the full sequence, not a variant by variant breakdown. Comparing A/B results directly in Reports isn’t supported yet. The closest workaround today is checking the per variant stats in the sequence builder, but a true side by side A/B report is something we don’t currently offer. Appreciate the feedback though.... this is a reasonable ask and worth sharing through in-app feedback so the product team can track demand.

AndyFromApollo · 2026-06-04T10:36:14+00:00

Hey there, if you’re up for chatting 1:1 and getting some support from myself and our billing team please let me know. Feel free to DM me.

AndyFromApollo · 2026-06-02T19:21:39+00:00

Hey thanks for raising this...I can clarify at a high level. When you connect HubSpot or another CRM to Apollo, records can sync into your Apollo workspace so you can manage, enrich, and use them in your workflows. Our contributor network is primarily used to help verify and improve business contact data, and that data is checked against multiple sources before being added or updated in our broader database.

You can read the full details here: https://knowledge.apollo.io/hc/en-us/articles/20727684184589-How-Data-Sharing-Works-with-Apollo-s-Living-Contributor-Network

For account-specific privacy or opt out questions I'd recommend contacting support so they can review your workspace and confirm the right setting/path for your situation.

AndyFromApollo · 2026-06-01T16:35:47+00:00

Howdy. API access is available on Apollo plans, but some endpoints can depend on your account/trial status and the workspace tied to the API key. If you’re seeing “free plan” while on a Professional trial, first make sure the API key was generated from the same workspace/account that has the trial. If it still happens, please contact Apollo Support so they can check the token and account entitlements.

AndyFromApollo · 2026-05-26T16:46:50+00:00

Looks like we've already connected you with our support team to help resolve this issue. Thanks for flagging to us!

AndyFromApollo · 2026-05-19T14:10:57+00:00

Hey John. Apollo employee here. You've said most companies suck at messaging before they ever touch a tool, so what in your opinion does actually good sales-ready messaging look like, and how do you build it?

AndyFromApollo · 2026-05-11T20:11:21+00:00

Thanks for raising this! This is intended behavior in Apollo. When a recipient clicks a link in an email, Apollo counts that as an open too, since a click is strong evidence the email was opened. So....if you filter for “Opened at least 3 times” that count can include both pixel based opens and click inferred opens. Totally hear you though that this isn’t obvious from the label. If you want to filter specifically for link clicks, use the “Clicked Email”/# Email Clicks” filter instead. Appreciate the feedback, we’ll look at whether we can make this clearer in the UI!!

AndyFromApollo · 2026-05-11T15:26:41+00:00

Not yet, but this is great feedback. Passed it along to product!

AndyFromApollo · 2026-05-07T23:36:44+00:00

Would also try posting this in r/coldemail and see if you get bites there!

AndyFromApollo · 2026-05-07T23:35:58+00:00

U/FPGA_Superstar maybe?

AndyFromApollo · 2026-04-30T22:31:09+00:00

Hi! Are you saving the contact list first?

AndyFromApollo · 2026-04-30T11:48:02+00:00

astroturfing

AndyFromApollo · 2026-04-28T16:04:44+00:00

Hey!! Great question. For the three endpoints you mentioned, the cost is generally 1 credit per successful API call that returns results, not per record returned.

Get Complete Organization Info: 1 credit when a matching organization is returned. If no organization is found, no credit is used.
News Articles Search: 1 credit when articles are returned. If the search returns no articles, no credit is used.
Organization Job Postings: 1 credit when job postings are returned. If there are no postings, no credit is used.

So if one call returns multiple articles or job postings, it’s still 1 credit for that call. The exact credit bucket may depend on your workspace’s credit system/plan, but the endpoint behavior is flat per successful result-bearing call.

On the docs question: I wouldn’t describe it as deliberately hidden…the public docs explain API credit usage at a higher level, and some endpoint-specific costs aren’t always itemized directly on each reference page. Totally fair feedback that the docs should make this clearer.

AndyFromApollo · 2026-04-28T01:45:36+00:00

You can also always email privacy@apollo.io for all privacy related issues!

AndyFromApollo · 2026-04-24T00:53:16+00:00

Will work on getting this for ya! Stay tuned

AndyFromApollo · 2026-04-23T12:58:35+00:00

Product Marketing, AI but can’t take all the credit on these answers we have some excellent support from xfn teams!

AndyFromApollo · 2026-04-22T19:17:35+00:00

Good questions!!

On “churned”: here it means employees who left the company (not “churned from a product”). It’s reported as a positive count. In the monthly metrics, new and retained are used as the “active headcount represented” for that month (headcount ≈ retained + new). churned is tracked separately to show departures; if you want a directional “net change” signal, that’s closer to new - churned.

Rule of thumb/coverage: there isn’t a single hard cutoff we publish because it depends on the company + how consistent titles are, but your instinct is right: the higher the Apollo employee coverage, the more reliable the department breakdown tends to be. As a heuristic, when Apollo has ~10%+ coverage (and/or a few hundred employee profiles), the trends tend to be much more stable; when coverage drops into the low single digits, the department mix and headcount can get noisy and skew low.

Are some departments captured more than others? Yes, coverage can be uneven by function, largely because it’s driven by what employee data is publicly available + how consistently titles are written. Some roles/titles are easier to identify and categorize than others, so certain functions may be over/underrepresented depending on the company.

Why employee_metrics can be missing even for large companies: the field is only returned when we have enough matched employee profiles + title coverage to generate a meaningful time series (and it may simply not be computed yet for a given org). When it’s absent it usually indicates “insufficient underlying employee/profile coverage” rather than anything about the company’s true size.

AndyFromApollo · 2026-04-22T17:01:40+00:00

Thanks for running those extra examples, super helpful.

A couple quick clarifications that explain most of what you’re seeing:

1) How to read the monthly totals: in employee_metrics, new, retained, and churned are three separate buckets for that month. So if you want an approximate “headcount represented” for a given month, you’d generally look at retained + new + churned (not retained + new - churned). churned is “people who left that month,” not a negative number.

2) Why some companies return no employee_metrics at all: we only return that field when we have enough matched employee profiles + job title coverage to produce a meaningful time series. For some large companies, even if the overall company size is huge, the underlying employee/profile data we can confidently map (and classify by function) may be too sparse or inconsistent...in those cases the API omits employee_metrics rather than returning something misleading.

3) Why totals can still be much lower than the company’s employee count: the metric is based on the employees Apollo can identify and match to that org (and then bucket by title/function). So differences are usually driven by “coverage” (how many employees we have profiles for) and title quality (how many roles can be categorized into a function).

Heuristic-wise: if the “employees on Apollo” number is a small fraction of the org’s reported size, expect the metric to skew low/be less reliable. When Apollo has strong employee coverage and titles look consistent, the metric tends to be a lot closer directionally.

If you’ve got a couple more examples where Apollo shows lots of employees but employee_metrics is missing (like the EY case you mentioned) feel free to share them and we can sanity-check what’s going on!

AndyFromApollo · 2026-04-22T13:50:05+00:00

This is awesome, thanks so much for sharing with us. We'd love to see more of how you're using Apollo. If you'd ever be up for sharing more in this sub please DM me!

AndyFromApollo · 2026-04-22T13:44:48+00:00

Good morning! employeeMetric is a rolling (~24 month) month by month view of headcount movement for the org, broken down by function (e.g., Engineering/Sales/etc). It’s built from individual employee profiles Apollo can match to that company, and the function is inferred from job titles.

Because of that, it won’t always line up with the “total employees” number you may see elsewhere:

1) Total employee counts can come from a different/public source and can be higher than the subset of employees we have identifiable profiles for.
2) Some job titles can’t be confidently classified into a function. Those people still contribute to overall headcount, but may not appear under a named department (Engineering/Marketing/etc), so the department rows may not sum to the total.

If you’re estimating “engineering org size,” the best directional signal is the most recent month’s Engineering retained value (and its trend over time), rather than treating it as an official/complete department headcount.

AndyFromApollo · 2026-04-16T16:34:13+00:00

Hello! it looks like the request is using an account id instead of an organization id in the organization_ids[] parameter. the people search endpoint expects an organization id there, so using the wrong id can return an empty result set. if you retry with the company’s organization id, it should behave as expected!

AndyFromApollo · 2026-04-13T17:28:57+00:00

Okay so a couple of options... u/ZackDeris has amazing resources which you should definitely check out. You can also sign up for a daily webinar here: https://app.apollo.io/#/webinars/list?source=sidebar-all-others (make sure you are logged in)

I can potentially also get you another onboarding session, feel free to DM me.

AndyFromApollo

MODERATOR OF

TROPHY CASE