Selligent Client Bundle Laravel Package

Product Decisions This Supports

• Feature scope: marketing automation integration. Determines whether the product syncs contacts, segments, consent flags, and campaign/transactional triggers into Selligent directly from the application, versus relying on manual exports, CSVs, or middleware (iPaaS/ESB).
• Build vs. buy vs. wrap. This package is effectively a "wrap" option: a pre-built PHP/Symfony client for the Selligent API instead of a custom integration layer. It shifts the decision from "do we spend 4–8 engineer-weeks on an API client?" to "do we accept an unmaintained dependency and own it?"
• Roadmap sequencing. If lifecycle messaging (onboarding, win-back, cart abandonment, NPS) is on the roadmap, this package makes the first increment cheaper — useful for validating whether integrated campaigns move retention metrics before committing to a larger martech investment.
• Vendor lock-in posture. Adopting the bundle deepens coupling to Selligent's data model and API. This is a strategic decision about whether Selligent stays the system of record for audiences, or whether the product owns segments and pushes only events.
• Data governance. Because the integration moves PII (emails, consent, purchase history) across a boundary, it forces explicit decisions on consent capture, retention, EU data residency, and audit logging — decisions that are easier to defer if no integration exists.
• Use cases it unlocks: account/contact provisioning on signup, real-time transactional triggers (password reset-adjacent messaging, order confirmations), segment membership sync for targeted campaigns, and unsubscribe/consent propagation back into the product.
• Migration and exit planning. A thin wrapper behind an internal interface lets you swap Selligent for another ESP/CRM later without rewriting domain code — a decision worth making consciously now rather than during a renewal negotiation.

When to Consider This Package

Consider it when:

• Selligent is already the contracted marketing platform and the integration is a given, not an open question.
• The application is Symfony-based (this is a bundle, not a Laravel package — Laravel teams would only reuse the underlying client, and even then as a reference, not a drop-in).
• Your integration surface is small and stable: a handful of endpoints, batch syncs on a schedule, no hard real-time SLAs.
• You have PHP engineers who can read, fork, and maintain the code — and are willing to vendor it into the repo with tests and version pinning.
• You need a fast proof-of-concept to demonstrate value to marketing stakeholders before funding a proper integration.

Look elsewhere when:

• You need vendor support, an SLA, security patching, or a documented upgrade path. One star and zero dependents means no community, no issue triage, and no signal that anyone else has hit your bugs.
• You're on Laravel or a non-Symfony framework — the bundle's service wiring and config semantics won't transfer, and you'll spend more time stripping it down than writing a focused client.
• You need broad API coverage (full REST surface, webhooks, bulk import, error/retry semantics, rate-limit handling) or high-volume, near-real-time throughput.
• The integration is business-critical at launch — this should not be the only path for revenue-generating triggers without an internal owner and a test suite.
• Your security review requires provenance, published advisories, or a maintained release cadence.

Practical stance: treat it as a reference implementation to fork, not a dependency to require. Budget a spike (2–5 days) to confirm the Selligent API version it targets is the one you're contracted on, then wrap it behind your own MarketingClient interface so the exit cost stays low.

How to Pitch It (Stakeholders)

To executives: This is a small, free PHP connector that lets our product push customer data and campaign triggers into Selligent without building an API client from scratch. It's a time-to-market lever, not a platform commitment — it can shave weeks off the first release of lifecycle messaging and let us test whether integrated campaigns improve retention before we invest in a larger martech build. The caveat is support: it's a community project with essentially no adoption, so we should own it internally. Recommendation: fund a short spike, adopt it as a vendored, tested component behind our own interface, and keep the option to swap providers open at renewal.

To engineering: It's a Symfony bundle wrapping the Selligent client — useful as a starting point, not as a dependency. One star, no dependents, no maintenance signal. Plan to fork it, pin it, add integration tests against a Selligent sandbox, and hide it behind an internal abstraction so the domain layer never imports its classes. If we're not on Symfony, budget the extraction work explicitly rather than assuming reuse. Define the failure modes up front: retries, rate limits, partial-failure handling on batch syncs, and what happens to a campaign trigger when Selligent is unavailable.

To marketing/ops stakeholders: This connects the product to Selligent so contact and segment data stay in sync automatically instead of through manual uploads. Expect faster campaign turnaround and fewer data discrepancies, but the initial scope is limited to the flows we explicitly build — it is not a full Selligent feature port.