Install the FXMacroData redistribution pixel

1. Register every website domain

Adding Commercial Redistribution asks for the first distribution surface before checkout, so the licence always starts against a known destination and access is enabled straight away. To add more domains afterwards, open API Management and register every other website domain that will display FXMacroData-powered data. You can add as many domains as you need, and adding a domain does not create a separate licence fee.

Non-web surfaces: register, then meter or report

In API Management, add each mobile app, desktop app, browser extension, Telegram or Discord bot, Slack app, AI assistant, email newsletter, community, or other display surface. There is no pixel, no bot check, no manual review, and no approval queue: registering the surface enables access immediately. How the audience is measured then depends on the kind of channel.

A typed-in figure still works for any surface you have not instrumented yet: enter the additional unique people reached during the billing period, excluding anyone already counted by the website pixel or by a backend report. Whichever route you use, every surface feeds one combined total, and that total determines the USD 10-per-100-user quantity.

Authenticated channels also state a declared audience when they are registered. It is not a billing input - billing uses what is measured - but the licence requires the figure on record.

2. Install the pixel where the data appears

For a conventional site, load the generated script on every page that displays FXMacroData data or derived output. It does not need to load on unrelated account, legal, profile, or marketing pages. For a single-page app, place it once in the global layout and use exposure mode so only the relevant data modules count toward the measured audience.

<script
  async
  src="https://fxmacrodata.com/static/js/fxmacrodata-pixel.js"
></script>

The script creates an anonymous browser identifier, records data-page and app-route exposure, sends a lightweight heartbeat after 15 seconds, and captures attribution-link clicks. Billing is based on the combined measured non-bot audience across all registered domains. You do not send customer account data to use the meter.

For single-page apps where only some sections display FXMacroData-powered output, add data-fxmd-meter-mode="exposure" to the script and mark the visible sections as metered modules. In exposure mode, loading the app shell verifies the pixel, but billing starts from module exposure events.

3. Put it in the right framework file

The goal is simple: the pixel must load once on every public page where your product can render FXMacroData-powered data. Common placements are below; the pixel integration guide has a copy-paste recipe for each one, and for another thirty platforms.

4. Mark React and SPA exposures

Do not mount and unmount the pixel script for each React tab. Install the pixel once, then tell the meter when a user can actually see a section powered by FXMacroData. Exposure mode does not require separate routes or a full page reload. The pixel deduplicates repeated views client-side and billing is based on unique non-bot users in each billing period, not view count.

<script
  async
  src="https://fxmacrodata.com/static/js/fxmacrodata-pixel.js"
  data-fxmd-meter-mode="exposure"
></script>

Automatic visible-section tracking

<section data-fxmd-metered data-fxmd-module="calendar">
  <CalendarPanel />
</section>

Explicit React hook

useEffect(() => {
  if (activeSection === "calendar") {
    const pixel = window.FXMacroDataPixel || { q: [] };
    if (pixel.trackModule) {
      pixel.trackModule("calendar");
    } else {
      pixel.q.push(["trackModule", "calendar"]);
      window.FXMacroDataPixel = pixel;
    }
  }
}, [activeSection]);

Use stable module names such as calendar, cot, macro_non_usd, news, widgets, or reports. The module name is used for diagnostics and auditability; the invoice still uses unique measured users.

5. Show attribution with a linkback

Redistribution requires visible attribution where FXMacroData-powered data appears. Add the generated link in your footer, data table area, chart footer, or dashboard shell, or use this minimum valid link:

<a
  data-fxmd-attribution
  href="https://fxmacrodata.com/"
  target="_blank"
  rel="noopener"
>
  Data powered by FXMacroData
</a>

The pixel checks whether the attribution element exists, is visible, and links to FXMacroData. API Management may add UTM parameters based on a registered domain for referral reporting, but those parameters are optional for verification. If you prefer not to add a separate link manually, API Management also provides an optional script mode that injects a small attribution link automatically.

6. Verify the installation

After installing the script and attribution, open each registered website in a normal browser. Then return to API Management. The redistribution panel shows the registered surfaces, combined users, pixel status, self-reported non-web audience, and estimated next invoice.

7. Use the API from your server only

The redistribution API key is server-side only. Do not expose the key in browser code, client-side bundles, mobile apps, or public repositories. Your server should request FXMacroData, cache what is needed for your product, and render human-readable user-facing views.

Commercial Redistribution has no separate request allowance. Your redistribution key draws on the monthly allowance of the Individual or Enterprise subscription it is added to, under the same fixed operational guards of 300 requests/minute, 5,000 requests/hour, and 20 concurrent requests. Because your server caches and refreshes on a schedule, your call volume should track how much data you display and how often you refresh it — not how many people view it.

Billing examples

Commercial Redistribution is an add-on to an active Individual or Enterprise subscription. After the trial it is billed at $10 a month per audience block, starting at one block whatever your audience size. A block covers up to 100 measured users or recipients, or up to 1,000 declared followers on a public social or broadcast feed. The blocks from automatically measured websites, backend-reported apps and bots, reported newsletters and private channels, and declared public feeds are added to one account-level quantity. Registering another surface creates no separate fee.

Billing blocks meter your audience only. They do not add or remove API requests: the request allowance is the one your underlying subscription already includes.