Hi there, We are evaluating several feature manag...
# ask-questions
r
Hi there, We are evaluating several feature management and experimentation platforms for a key business initiative, and your solution is on our shortlist. We are looking for a server-side tool that allows our team to manage URL redirects from a simple dashboard. Our primary use case is to route traffic from a single starting URL to different destination pages based on URL parameters. The unique challenge is that the tool's SDK will be implemented on a third-party partner's website, requiring a clear separation between their technical setup and our ongoing campaign management. Our use case is very specific and has some critical technical requirements. Before we proceed, we need to confirm if your platform can support our exact needs. Our Operational Model & Core Requirements: 1. Partner Implementation & Support: We will be working with a large partner company whose developers will perform a one-time, server-side integration of your SDK into their blog's backend. ◦ Onboarding: Do you offer free onboarding support to guide our partner's development team through this process? What are your typical support response times for implementation-related questions? ◦ Setup Time: What is the average time required for a developer to complete this initial SDK integration? ◦ Security Scoping: Is it possible for the developers to limit the SDK's execution to a specific URL path (e.g., only run on
<http://partner.com/blog/*|partner.com/blog/*>
)? This is a critical security requirement to ensure our rules can only affect a designated part of their website. 2. Separation of Concerns (Critical): Our operational model requires a clear separation of duties. The partner's developers are responsible for the one-time technical integration, while our team manages the ongoing campaign strategy. Therefore, the platform must ensure that our campaign rules, targeting logic, and destination URLs are managed exclusively through your dashboard and are not visible or configurable within the partner's backend code. 3. Server-Side Execution: The entire process must be server-side to avoid any client-side "flicker effect." Client-side JavaScript-based redirects are not a viable solution for us. 4. Primary Use Case (Rule-Based Redirect): We need to route traffic from a single starting URL to various destination landing pages based on URL query parameters. For example: ◦ A user visiting
<http://partner.com/base-url|partner.com/base-url>
(with no specific parameters) sees the default landing page. ◦ A user visiting
<http://partner.com/base-url?utm_campaign=campaign_1|partner.com/base-url?utm_campaign=campaign_1>
must be instantly redirected to
<http://partner.com/lp1|partner.com/lp1>
. ◦ A user visiting
<http://partner.com/base-url?utm_campaign=campaign_2|partner.com/base-url?utm_campaign=campaign_2>
must be instantly redirected to
<http://partner.com/lp2|partner.com/lp2>
. 5. Parameter Stripping & Replacement (Critical): When a redirect occurs, we must have full control over the final URL's query parameters. The original trigger parameter (
?utm_source=meta
) must be completely stripped, so the end client cannot see our operational logic in their analytics. We must be able to define the final URL to be either a clean URL (
<http://client.com/product|client.com/product>
) or one with custom-set parameters (
<http://client.com/product?utm_source=partnerblog|client.com/product?utm_source=partnerblog>
). Our Questions: 1. Can your platform fully support the operational model and all of the core functional requirements listed above? 2. Regarding Requirement #5 (Parameter Stripping), does your platform offer a native feature to manage this server-side, or would this require custom logic to be written by the implementing developers? 3. What are your typical support response times for ongoing technical inquiries (post-implementation) for a customer on your free plan? This is a key strategic project for us, and the platform we choose will be a long-term partner. We appreciate you taking the time to address these specific points. Best regards, Moritz
f
Hi Moritz:
Thanks for the detailed requirements. To answer your questions: 1. Yes, we can support that mode of operating. We work server side and client side (and even on CDN edge workers) 2. Server side redirect will require the technical team implementing to add some simple code to grab the URL paramters to set as "attributes" in the SDK implementation. What I would probably do is have one master "redirect" flag, that would contain all the rules (on the growthbook side) for the request params, and what destination to go to from that. The team implementing this flag would grab the value of the flag, and redirect to whatever value is being returned by the SDK- the ruleset as to how to do this would come from the payload in GrowthBook, and not need to change per URL or param (or future params). 3. Support response times depends a bit on the plan you're on - Pro has live chat as well as email support, and Enterprise includes a support SLA, and shared Slack/Teams channels. We also like to create long term relationships with our customers, and we would welcome the opportunity to show you how we can meet your needs.
Feel free to DM me and we can set up some time to chat