In your app
A controller answers a route on your app: it callslistConversionDefinitions() and returns the answer.
Add the controller
app/Http/Controllers/ListConversionDefinitionsController.php
Add the route
routes/web.php
Call it
Terminal
php artisan serve running, it prints its answer as JSON.Call it from the terminal
Terminal
listConversionDefinitions() on your default site and prints its answer as JSON. See Call any method from the terminal for every argument type.
Another system uses it to find the Conversion to post facts to: triggers.external: true accepts POST /conversion-event/external, naming the Conversion by its id or key.
Parameters
Parameters
None: call it with no arguments.
Returns
Returns
A
ListConversionDefinitionsResponse (Fetchski\AttractCmsLaravel\Data\ListConversionDefinitionsResponse). The enabled Conversions. Read its properties ($listConversionDefinitions->conversions): each says whether the site always sends it.Errors
Errors
Nothing to catch: the SDK retries what is safe, and Laravel logs and renders the rest (see Errors and testing).
The API key is missing, malformed, unknown, disabled, expired or archived (
invalid), or a request that must be signed — by the route, or by the key’s own signing mode — has a missing, stale or wrong signature (an upload signs its SHA-256, declared in X-Fetchski-Content-SHA256, in the body’s place) (unauthorized).Retried first: No. Read: siteMessage(), errorName(), data().The API key lacks the scope this route needs (the message names it), or the key is used from an address outside its allowlist.Retried first: No. Read:
siteMessage(), errorName(), data().Nothing with this identifier — or the caller may not use the Data API at all (anonymous visitors and non-admin sessions get 404 so the API is not advertised). A write while conversion tracking is switched off also answers 404.Retried first: No. Read:
siteMessage(), errorName(), data().The key used up its reads- or writes-per-minute limit (set per key; defaults 600 / 120). Still, after the client’s own waits and retries.Retried first: Yes: the client waits
Retry-After (1 s when absent; over 60 s it gives up at once) and retries, up to retries times (2 by default). Read: retryAfter() (seconds, or null), siteMessage().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: 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().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 status, or a success whose JSON doesn’t match this SDK version’s types (update the SDK).Retried first: No. Read:
reason(), status().Attract::site('acme') named a slug that isn’t under sites in config/fetchski-attract.php.Retried first: No: nothing was sent. Read: getMessage(), $e->slug.Behavior
- Access: an API key with
conversions:read— or its group masterads:all, oradmin:all— or a signed-in user holding theconversion-events:viewpermission. Anonymous callers get 404. - Rate limit: the key’s own reads-per-minute limit, set when the key is created (default 600); over it, 429 with
Retry-After. The client waits and retries for you; you seeRateLimitedonly if that runs out. - 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
timeoutinconfig/fetchski-attract.phpfor longer.
Test it
It calls the route above with the SDK faked: the fake answers every call with a valid example, so nothing leaves your machine and no config or key is needed. Save it astests/Feature/ListConversionDefinitionsTest.php, then run your tests:
tests/Feature/ListConversionDefinitionsTest.php
Terminal
Related
Conversions the page can fire (public)
Attract::conversions()->listActiveConversions()GET /conversion/definitions
The endpoint this calls, in the API reference: the HTTP request and answer, and every rule the site checks.