Skip to main content

In your app

A controller answers a route on your app: it calls listActiveConversions() and returns the answer.

Add the controller

app/controllers/list_active_conversions_controller.ts

Add the route

start/routes.ts

Call it

Terminal
With node ace serve running, it prints its answer as JSON.
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. Your exception handler turns them into your app’s own answers, once for every call (see Map SDK errors to responses); catch only what you want to react to here.
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 config/attract.ts doesn’t list (with the keys in the database: no row in attract_api_keys).Retried first: No: nothing was sent. Read: message, slug.
setup
The site’s entry is wrong: a malformed baseUrl or key, a key filed under another slug, or no default site. node ace attract:check names the fix.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) in config/attract.ts for longer.

Test it

It calls the controller above with the SDK faked: fakeAttract() puts the fake in the container for this one test, and it answers every call with a valid example, so nothing leaves your machine and no key is read. Save it as tests/unit/conversions_list_active_conversions.spec.ts, then run your tests:
tests/unit/conversions_list_active_conversions.spec.ts
Terminal

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.