Weave Code
Php Sdk Laravel Package
clicktrail/php-sdk
A PHP SDK for integrating ClickTrail into Laravel and other PHP applications. It provides a simple, lightweight client for connecting to ClickTrail services, sending requests, and handling responses, so you can add tracking and event workflows quickly with minimal setup via Composer.
Deterministic PHP engine for parsing observed acquisition context, applying first/last-touch rules, and building canonical events.
Frequently asked questions about Php Sdk
- How do I install clicktrail/php-sdk in a Laravel app with Composer?
- Install it with composer require clicktrail/php-sdk and pin the constraint to 0.1.x while the package is pre-1.0. After install, publish any package config and bind your ClickTrail endpoint and credentials in a non-production environment first. Verify the composer.json extra.laravel block and the registered service provider before assuming auto-discovery works.
- Does clicktrail/php-sdk ship a Laravel service provider and facade?
- The release notes do not confirm that a service provider, publishable config, or facade exists, so treat the Laravel packaging as unverified until you inspect composer.json and the src directory. A service-provider-bound client plus a config file and facade is the idiomatic expectation for this kind of package. If they are absent, resolve the client from the container manually or write a thin wrapper provider in your app.
- Which Laravel and PHP versions does clicktrail/php-sdk support?
- No published support matrix is included in the release notes, so the safe assumption is a standard PHP 8.x runtime, with Laravel 10, 11, and 12 as likely targets. Confirm the constraints in composer.json before adopting it, and test on your exact PHP minor and Laravel major. Applications on older Laravel majors or serverless hosting with limited workers should be assessed as a separate, higher-effort track.
- How does the consent model work in clicktrail/php-sdk?
- The package gates tracking on a consent state, but the notes do not say whether that is a simple boolean, a granular category model, or a CMP integration, and whether state is persisted and re-evaluated. This is the highest compliance-risk unknown in the release, because the wrong assumption has legal exposure, not just engineering cost. Confirm the semantics with the maintainer before wiring it into production consent flows.
- What do first-touch and last-touch attribution rules mean in ClickTrail?
- The SDK is a deterministic engine that parses observed acquisition context, applies first-touch or last-touch rules, and emits canonical events plus attribution results. Determinism is asserted for the core under golden fixtures, but behavior under clock skew, out-of-order events, late-arriving conversions, and timezone differences is not established. Validate those edge cases against your own event shapes before replacing an existing tracking path.
- Is the clicktrail/php-sdk BatchClient queue-based, and how does it handle retries and failures?
- BatchClient is described only as buffered egress to an upstream endpoint, so it is unclear whether it is synchronous, queue-backed, or fire-and-forget. Flush cadence, retry policy, ordering guarantees, idempotency keys, dead-letter handling, and backpressure behavior are undocumented. Confirm these semantics and that your app already runs supervised queue workers before committing to this design.
- Is clicktrail/php-sdk stable enough for production at version 0.1.0?
- At v0.1.0 there is no semver guarantee on the public surface, so config keys, DTO shapes, and the consent API can change in a minor bump. The test suite is also thin in absolute terms, with 11 tests spread across attribution, consent, and transport, leaving consent edge states and transport error paths unproven. Pin versions, gate every upgrade behind a review, and run a dual-write shadow period before cutting over.
- How can I test clicktrail/php-sdk with the golden fixtures in CI?
- The release claims 57/57 field parity and 12/12 golden fixtures, which is the strongest signal in the package, but the notes do not confirm the fixtures ship in the repo or run in CI. Ask the maintainer to confirm their location and how to invoke them. In parallel, build a small internal fixture set derived from your production event shapes so you can validate the package independently during a shadow period.
- What are the alternatives to clicktrail/php-sdk for server-side attribution in Laravel?
- Realistic options include building a small in-house attribution service, using the GA4 Measurement Protocol, adopting a CDP or event pipeline such as Segment or server-side GTM, or keeping the current tracking path. The choice depends on whether you specifically need a deterministic first/last-touch core validated field-by-field. Because this package is new with no incumbent wrapper, compare total integration and migration cost, not just feature lists.
- How do I configure ClickTrail credentials and publish the config file in Laravel?
- Publish the package config to config/clicktrail.php if the provider supports it, then wire the endpoint and credentials through environment variables in a non-production environment first. Keep secrets out of version control and confirm the expected key names against the installed version. Config keys may change before 1.0, so pin the package and review the config diff on every upgrade.
Weaver
How can I help you explore Laravel packages today?