Skip to main content

In your app

A function makes the call on the client it is given, so your code passes the real one and a test passes a fake.

Add the function

src/attract/list-active-conversions.ts

Call it

A script makes the client once and calls the function:
scripts/list-active-conversions.ts
Terminal
A route handler, a job or a queue worker calls it the same way.
Each enabled Conversion with a browser trigger, compiled, with only its rows sent from the page and its page-view triggers resolved against path to a yes/no. No names, no server-only IDs, and never the site’s page list. Integrations should use GET /conversion/definitions instead.
One object, e.g. listActiveConversions({ path }); leave out the optional fields.
string | null | undefined
Optional. Leave it out and the site uses "/". The page path the conversions are for. Default /. At most 2048 characters.
A ListActiveConversionsResponse. The page’s conversions. Read its properties (listActiveConversions.conversions): each says whether the site always sends it.
readonly ListActiveConversionsResponseConversionsItem[]
Always sent. A list of ListActiveConversionsResponseConversionsItem.
Nothing to catch: the SDK retries what is safe, and throws the rest as the classes below; catch only what you want to react to (see Errors and testing).
5xx
The site failed (or something in front of it did). Its logs say why.Retried first: A 502, 503 or 504: yes, after 0.5 s then 1 s. A 500: no. Read: siteMessage, errorName, data.
no answer
No answer: DNS, a refused connection, TLS, or the timeout (15 s per attempt by default).Retried first: Yes, after 0.5 s then 1 s. Read: reason, neverConnected.
not sent
The client refused to send it (e.g. a path segment of ..); the site never saw it.Retried first: No. Read: reason (what to change).
any other
Any other status, or a success whose JSON doesn’t match this SDK version’s types (update the SDK).Retried first: No. Read: reason, status.
setup
sites.forSite('acme') named a slug your sites (createSiteClients()) don’t have.Retried first: No: nothing was sent. Read: message, slug.
setup
The client’s settings are wrong: no FETCHSKI_ATTRACT_URL (or baseUrl), or a malformed API key.Retried first: No: nothing was sent. Read: message (what to fix).

Behavior

  • Retries: a read is safe to repeat: the client retries it on no answer, a 502/503/504 and a 429.
  • Timeout: 15 s per attempt by default; raise timeout (milliseconds) on the client for longer.

Test it

It calls the function above with a fake client: the fake answers every call with a valid example, so nothing leaves your machine and no settings or key are needed. Run it with node --test.
tests/conversions-listActiveConversions.test.ts

List the enabled Conversions

site.conversions().listConversionDefinitions()

GET /conversion/active

The endpoint this calls, in the API reference: the HTTP request and answer, and every rule the site checks.