Install guide / Web channel

Install FXMacroData on Client portal

Your meter

Client portal is measured by the redistribution pixel.

One script tag in the browser counts unique non-bot visitors. You report nothing and you maintain no number.

You do not use the backend audience endpoint. It exists for surfaces with no browser to run the pixel in, and a report made against a website surface is rejected, even when your own server knows exactly who signed in.

Pixel integration guide What Client portal costs API Management

Setting it up

  1. 01

    Register the Client portal domain

    Add the exact origin in API Management. Apex and www alias each other; every other subdomain is its own entry.

  2. 02

    Load the tag in exposure mode

    Mount the tag inside the authenticated portal shell. A login wall does not exempt a surface: a client who is shown the data is a measured user. Exposure mode counts a visitor only when a tagged component is actually shown, which is what you want when the data sits behind a feature the customer switches on.

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

    Tag the components that show the data

    Tag the report views and data panels. White-labelling the presentation is fine; passing the raw feed through to the client as an API is not.

    <div data-fxmd-metered data-fxmd-module="calendar">
  <!-- FXMacroData output -->
</div>
  4. 04

    Keep the attribution visible

    A visible link back to FXMacroData has to sit wherever the data is, including in anything you export.

The rule that matters

Call the FXMacroData API from your backend, never from browser code. The pixel is the only thing that belongs in the page.

Confirming it works

  1. 1 Open a page that shows FXMacroData output in a normal browser.
  2. 2 Confirm a POST to https://fxmacrodata.com/fxmacrodata-pixel/v1/events returns 202 in the Network tab.
  3. 3 Open API Management and confirm the pixel shows as active.

Reference

Shared detail that applies to every web channel, kept in one place rather than restated here.

Content Security Policy and consent

Both script-src and connect-src, plus what is stored on the device.

What the collector validates

Origin matching, and what the bot filter does and does not weigh.

Self-hosting and relaying

Pin your own integrity hash, or proxy the collector through your domain.

Verify and troubleshoot

Every symptom, its cause, and its fix.

Other channels using the redistribution pixel

Same meter, different setup detail.

Website Web app SaaS product Customer dashboard Embedded widget Documentation site Landing page

Every channel install guide

Summarize article with AI:

ChatGPT Perplexity Claude Grok Gemini Mistral

AI Answer-Ready

Key Facts

Page
Client Portal
Section
Documentation
Canonical URL
https://fxmacrodata.com/documentation/redistribution/client-portal
Source
FXMacroData editorial and official publisher references
Last Updated
See page metadata

Provenance And Trust

Cite the canonical URL and source field above. Where available, this page maps to official publisher releases and timestamped updates.

Quick Q&A

What is this page about? This page explains Client Portal with directly usable context for trading, research, and API workflows.

What source should be cited? Use the canonical URL and the listed source field; cite official publisher references when available.

How fresh is this content? The last updated value above reflects the page metadata or latest available data timestamp.

Can this be used in AI assistants? Yes. This section is intentionally structured for retrieval and citation in chat assistants.

Prompt Packs

Use these in ChatGPT, Claude, Gemini, Mistral, Perplexity, or Grok for consistent source-aware outputs.

Share page X LinkedIn Email