- Can I install proglab/selligent-client-bundle in a Laravel application?
- Composer may install it, but this is a Symfony bundle and will not register its services, configuration, or compiler passes in Laravel's container. Laravel has no bundle equivalent, so you would need to consume or port the underlying client through a custom service provider. Treat the bundle as reference source rather than a direct dependency in a Laravel app.
- Does this package support Laravel 10 or 11 and PHP 8.2 or 8.3?
- The package is described as a Symfony 5 bundle, so Laravel version support is not declared. Any Laravel 10/11 or PHP 8.2/8.3 compatibility depends on the underlying Selligent client being framework-agnostic and installable on your target platform. Review composer.json constraints and run composer audit before assuming it will work.
- How do I integrate Selligent with Laravel if this is a Symfony bundle?
- First confirm whether the bundle delegates to a standalone, framework-agnostic Selligent client library. If it does, bind that library's credentials and options in a Laravel service provider, resolve the client from the container, and wrap contacts, segments, and campaigns behind your own domain services. Avoid depending on Symfony HttpKernel, EventDispatcher, or bundle config classes in your Laravel code.
- Which Selligent API does this package target, SOAP or REST?
- The overview says it wraps Selligent's REST API for contacts, segments, and campaigns, but the exact API surface and version are not clearly documented. Classic Selligent integrations often used SOAP/XML, while Marigold Engage has been moving toward REST. Confirm the targeted API generation and version in the source code or with the maintainer before committing to the integration.
- Is proglab/selligent-client-bundle maintained and safe for production?
- The signals are low: a single maintainer, no dependents, and minimal community activity suggest the project may be dormant. Unmaintained packages can accumulate unpatched transitive dependencies, so run composer audit and review PHP and Symfony constraints. For production use, plan to fork and own the code rather than rely on upstream fixes.
- What are the alternatives to using this Symfony bundle in a Laravel app?
- The best alternative is usually to consume the underlying Selligent or Marigold Engage client library directly, assuming it is framework-agnostic. You can also call the Selligent REST API with Laravel's HTTP client and build a small, testable integration layer with your own DTOs, retries, and logging. If you need long-term support, evaluate actively maintained Marigold Engage SDKs or a custom client rather than this bundle.
- Do I need Selligent credentials or a sandbox tenant to test this package?
- Yes, Selligent and Marigold Engage are contract-gated and per-tenant, and APIs are often IP-allowlisted. You cannot validate the integration in CI without a provisioned sandbox tenant and credentials, so budget procurement lead time. Build a fake or mock HTTP layer for local tests so your test suite does not depend on live access.
- How should I handle contacts, segments, and campaigns from Laravel using this package?
- Expose narrow domain services in Laravel, such as ContactSync, SegmentQuery, and CampaignTrigger, that call the underlying client. Keep Selligent field mappings, consent attributes, and segment definitions in configuration or database tables you control. Add idempotency keys, retries, and dead-letter handling because marketing automation calls can fail silently.
- What are the GDPR and consent risks of integrating Selligent with Laravel?
- This package moves contact records and marketing consent state, so silent failures can become compliance incidents such as stale unsubscribes or consent drift. You need audit logging, reconciliation jobs, and explicit error handling around consent updates. Treat consent propagation as a critical path, not a background nicety.
- Is there a test suite that mocks the Selligent API?
- There is no evidence of a test suite from the package signals, which show a single star and no dependents. Assume you will build your own harness that mocks HTTP responses for contacts, segments, and campaigns. That harness is essential before touching a live tenant and should cover failures, retries, and consent edge cases.