Campaign Launch & Tracking Integrity Auditor

Audit campaign links before launch.

This Actor performs an HTTP-only technical audit for one declared campaign launch. It observes DNS resolution, connections, HTTP redirects, final status, final destination and query parameters. It then evaluates the rules supplied for that campaign and reports evidence for every requested asset.

It answers: do these campaign links obey the declared technical contract? It does not determine whether an entire campaign is correct or commercially successful.

Input

Provide a campaignName and one to 1,000 assets. Each asset has a required public HTTP(S) url and an optional unique id; omitted IDs are generated deterministically in input order.

Optional campaign rules are:

• requiredParams: parameters that must reach the final URL with at least one non-empty value.
• allowedFinalHosts: exact allowed final hostnames. Wildcards and implicit subdomains are not accepted.
• requireHttps: require HTTPS at the final destination.
• consistentParams: parameters whose single non-empty final value must be identical across all evaluable assets.

Only test URLs you are authorized to test. URLs must use HTTP or HTTPS, have no userinfo, use only default ports, and resolve only to public addresses. The Actor does not attempt to bypass authentication, access controls, rate limits, paywalls, or anti-bot protections.

Output

The default Dataset receives one structured row per requested asset, including the input URL, redirect chain, final URL and status when observed, parameter facts, rule results, findings, network outcome, audit status and billing disposition.

RUN_SUMMARY in the default Key-value Store is written only after all requested asset rows were delivered. It contains the campaign status, counts, campaign findings, and cross-asset consistency groups.

Input URLs, redirect URLs, final URLs and query parameters are stored as audit evidence. Do not place credentials, tokens or other sensitive values in URLs. Userinfo is rejected, but query strings may still contain sensitive values supplied by the user.

Status semantics

• READY: no asset or campaign finding of severity REVIEW or BLOCKER.
• REVIEW: an observation is incomplete or requires review, including access-restricted HTTP responses and campaign-wide inconsistency.
• BLOCKED: an asset-level blocker was observed, such as a 404/5xx final response, a required parameter missing at a known final URL, an unsafe redirect, or a redirect loop.

An HTTP response such as 404 is an audit result, not necessarily a failed Actor run. A run is failed only for invalid manifests or internal/delivery invariants that prevent a complete campaign result.

For consistentParams, the Actor reports groups of observed values. It never assumes the majority value is correct and never declares a minority asset wrong merely because it is different. If any necessary asset cannot be evaluated, that consistency result is NOT_EVALUATED, not PASS or FAIL.

Billing

The current model charges USD 0.001 for one asset-audited pay-per-event charge per completed, chargeable asset audit. Apify platform usage costs are charged separately to the user. Billing disposition is independent from READY, REVIEW and BLOCKED.

Final HTTP results, conclusively detected redirect loops and conclusively invalid redirect locations can be chargeable. DNS failures, unsafe destinations, TLS failures, connection failures, timeouts, access-restricted responses and incomplete redirects are not chargeable. Campaign-level findings do not create an additional event.

Before any network request, the Actor checks whether the run has capacity to charge the worst case: every requested asset. It refuses the whole run rather than processing a partial campaign. The configured primary event is asset-audited; there is no Actor-start charge and no automatic default-Dataset-item charge.

Limits and non-goals

This is not browser QA. It does not execute JavaScript redirects, parse HTML, take screenshots, validate forms, pixels, GA4, GTM, CRM, analytics events, SEO, accessibility, Core Web Vitals, creative quality, audiences, bidding, budgets, ROAS, or real-user behavior.

There is no history, baseline, monitoring, alerts, webhook, saved policy, automatic fix, proxy rotation, database, or external ad-platform import. Cookies are disabled, TLS verification remains enabled, and the Actor does not use an Apify Proxy by default. Websites whose behavior depends on cookies, login state, JavaScript or a browser may not be fully represented.