Core concepts
A handful of objects make up Converly. Once you know how they fit together, the rest of the API reads easily.
An account holds your sites and billing. Each site has its own flows and destinations. When a flow fires, Converly records an event and delivers the conversion to every destination the flow targets.
Conversion values
Every action can send a value with its conversion. The value is either a fixed amount you set on the action, or a dynamic value that comes from the trigger itself, like the total price of each Acuity Scheduling booking. A dynamic value lets your ad platforms optimise for your most valuable customers, instead of counting every conversion as worth the same.
A dynamic value is a reference on the action, config.conversion.valueSource, made up of a triggerId and a sourceId. The action’s fixed value and currency stay in place as the fallback, which Converly sends if a conversion ever arrives without a value from the trigger. It works the same way for every destination.
To see which values a site’s trigger can supply, call List value sources. To set one up in the dashboard instead, see Send dynamic conversion values in the help centre.