Rate Limit

Data & Tracking

Also: API Rate Limiting · Throttling

Rate limit = maximum requests allowed per defined time window

What it controlsRequests per time window

When you hit itRequests get rejected or delayed

Set byThe platform or API you're calling

Common causeBulk syncs and reporting tools

Quick definition

A rate limit is a cap on how many requests a system will accept from you in a given time window, such as 100 requests per minute. Platforms like Google Ads, Meta and CRMs use rate limits to protect their servers from overload and stop any single user from hogging capacity.

How it varies across Australia

Rate limit issues show up more often in Australian businesses running multiple integrated tools against the same ad platform account, since agencies and in-house teams sometimes pull from the same API allowance without realising it. The pattern is common wherever reporting dashboards, CRMs and ad platforms are stitched together without a shared plan for API usage.

See data and tracking maturity across Australian industries →

What it actually means

Picture a nightclub with a bouncer who only lets in twenty people per hour. It doesn't matter how many people want in, or how important they think they are. Twenty an hour, no exceptions. A rate limit is that bouncer, applied to data requests instead of people.

Every major platform you connect to for marketing purposes, Google Ads, Meta, HubSpot, Salesforce, sets a rate limit on its application programming interface (API). This stops any one account from overwhelming shared server capacity. When you exceed the limit, the platform responds with an error instead of the data you asked for, or it queues your request for later.

This matters for marketers because rate limits sit quietly underneath most automated reporting and integration work. Your dashboard pulling live conversion data, your CRM syncing lead status, your attribution tool stitching together touchpoints. All of it runs through APIs that have a ceiling.

Most marketers never think about rate limits until a dashboard stops updating or a data sync silently drops rows. By then the missing data has already distorted a report or, worse, a decision made from that report.

A rate limit isn't a bug in your tooling. It's the platform telling you that you've asked for more than your fair share, right now.

How to calculate it

Rate limit = maximum requests allowed per defined time window

Worked example. A platform sets a limit of 200 requests per minute. Your reporting tool sends 250 requests in that minute because it's syncing three data sources at once. The platform accepts the first 200 and rejects or delays the remaining 50, meaning your dashboard is missing part of that minute's data.

The Australian context

Australian businesses often run smaller in-house teams stacking multiple tools against the same ad account. A single Google Ads or Meta account might be feeding a CRM, a business intelligence dashboard and an agency's own reporting layer, all pulling from the same allowance. Nobody individually exceeds a sane amount of usage, but combined they hit the ceiling regularly. This is more common in mid-market Australian businesses than in larger organisations, which tend to have a single centralised data pipeline rather than several tools querying independently.

Where people get this wrong

Assuming a missing data gap means tracking is broken.A rate limit failure looks identical to a tracking failure on the surface. Checking API response logs first saves hours of misdiagnosing a pixel or tag that was never the problem.

Running multiple tools against one account without coordination.Each tool assumes it has the full allowance to itself. Stack three or four and you'll hit the ceiling even though no single tool is misbehaving.

Retrying failed requests immediately and aggressively.Hammering an API right after being rate limited often extends the lockout or triggers a harder block. Most platforms expect a delay before retrying, not an immediate resend.

Common questions

How do I know if I've hit a rate limit?

Most APIs return a specific error code, often 429, meaning too many requests. If a dashboard or integration silently stops updating rather than throwing a visible error, check the tool's error logs or API status page before assuming your tracking itself has broken.

Can I increase a rate limit?

Sometimes. Many platforms offer higher limits for verified developer accounts, paid tiers, or approved partner status. Google Ads and Meta both have tiered API access based on account spend and usage history. It's worth asking your platform rep if reporting gaps are recurring.

Does a rate limit affect my ad performance directly?

Not usually. Rate limits affect reporting and data retrieval, not ad delivery or bidding. The risk is indirect, if your reporting is incomplete, you might make a budget or targeting decision based on partial data without realising it.

Why did my reporting tool suddenly start showing errors?

A common cause is adding a new integration or automation that increased total request volume against the same account, pushing combined usage over the platform's limit. Auditing which tools query the same API is the fastest way to find the culprit.

Debrief

Get the next one

No spam. No fluff. Just the next article, straight to your inbox.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →