hey guys i have a question around logged in/logged out users

# segment_user_key => anonymous_id/user_id
  # segment_user_id => anonid/current_user.id
  #
  def analytics_event_tracking
    Analytics.track(
      event: 'Experiment Viewed',
      segment_user_key => segment_user_id,
      properties: {
        experiment_id: experiment.id,
        variation_id: experiment.variation
      }
    )
  end

we were using this code in the backend to fire the experiment viewed event. My comment above shows what those values can be of course - what happens here though is we are potentially losing the context between logged in and logged out users. If somebody comes to the site, triggers an Experiment Viewed event while logged out, registers - then their user key/id will change (now its the logged in version) and so the goal when triggered will be presumably not be measured as it can't be matched? If we instead always use their logged out key - we lose the ability to track them across devices? That said, while looking at the docs https://docs.growthbook.io/lib/ruby#tracking I see that you recommend not sending user identifiers at all. Is that because if we kick this to Segment they'll just handle all of this? Send the logged in/logged out ID's and the query on your side looks for both? Be good to understand this a little more to make sure our implementation is bullet proof

Hi all! I'm trying out the local instance and I can't connect to Redshift because of the following error:

no pg_hba.conf entry for host <>, SSL off

- my data platform team tells me it's because I need to enable SSL, but i don't see it mentioned anywhere in the docs..

I'm working with the javascript SDK and running into an issue with features returning a null value rather than any expected value. GB object returns when I console.log(gb) however looking inside that object, the features return null values. When I try to use gb.isOn("my-feature") it always returns false. Am I missing something in my code, or is something likely wrong with my set up?

const gb = new GrowthBook({
            apiHost: "<https://cdn.growthbook.io>",
            clientKey: "sdk-z2eQdvHSoRomlSFH",
            // Enable easier debugging during development
            enableDevMode: true,
            // Update the instance in realtime as features change in GrowthBook
            subscribeToChanges: true,
            // Only required for A/B testing
            // Called every time a user is put into an experiment
            trackingCallback: (experiment, result) => {
              console.log("Experiment Viewed", {
                experimentId: experiment.key,
                variationId: result.key,
              });
            },
          });

          
          // Use an async function to initialize GrowthBook
          async function initializeGrowthBook() {
            // Download features and experiments from the CDN
            await gb.init();
            console.log("GrowthBook initialized");
          }
          
          initializeGrowthBook(); // Call the async function
          console.log(gb);
          if (gb.isOn("my-feature")) {
            console.log("Feature enabled!");
          }

Hi! We're integrating with Amplitude via BigQuery and ran into a few errors with the generated queries. I've managed to fix the Experiment Assignment Queries by changing

event_properties:experiment_id

to

event_properties.experiment_id

and so on, but now have errors with the generated metrics. I have "Unrecognized name: event_name; Did you mean event_time? at [17:15]" when looking at the metrics from the sidebar and "No matching signature for operator = for argument types: JSON, STRING. Supported signature: ANY = ANY at [28:7]" for query results. Not sure if this is a super edge case or something someone may have seen before?

How to QA a growthbook experiment

Hello! We can't figure out whether

evalFeature

function evaluates on the server ? We need to know whether distribution between buckets will work when we have several instances of servers. We use java-sdk

Hello, I am attempting to update the SDK to the latest version to begin using sticky bucketing and payload encryption. However, I am encountering an error. The app in question is a NextJS app (page router). I am unsure of what I might be missing. Can you please help me with this issue? This is the code in my

_app.js

file:

const growthbook = new GrowthBook({
  apiHost: "<https://cdn.growthbook.io>",
  clientKey: growthbookClientKey,
  enableDevMode: true,
  subscribeToChanges: true,
  decryptionKey: growthbookDecryptionKey,
  trackingCallback: (experiment, result) => {
    analytics.track(GA4_EXPERIMENT_VIEW, {
      experiment_id: experiment.key,
      variation_id: result.key,
    });
  },
});

function MyApp({ Component, pageProps }) {
//... Code omitted for brevity

    useEffect(() => {
    // Load features async
    let isMounted = true;
    if (isMounted && isReady && gaClientId) {
      growthbook.setAttributes({
        id: gaClientId,
        url: window.location.href,
      });
    }

    if (isMounted && isReady) {
      growthbook.loadFeatures({ autoRefresh: true });
    }

    return () => {
      isMounted = false;
    };
  }, [isReady, gaClientId]);

//... Code omitted for brevity
}

export default MyApp;

I understand that for react native and nodejs SDKs I need to add the

node:crypto

polyfill, but this is not my case here, any ideas on what I am doing wrong? SDK version:

"<@U052WVA1MH6>/growthbook-react": "^0.24.0"

Hey team, we are using Attributes for the first time to filter out users from our analysis. We are passing a boolean flag, which gets updated after our experiment flag is already triggered. We later update the boolean flag using .setAttributes(). It seems that the attribute is set correctly, which we confirmed using .getAttributes(). However, users are not getting filtered at all in our Experiments (we tried using Target by Attributes and Target by Saved Groups). We're stuck at this point and not sure how to proceed, so would appreciate any help.

Hi All, I've been looking for a way to change experiment variation values and weights using a single API call (also to add/remove additional variations). The only way I found is to call 2 APIs. First - update experiment while setting a list of variations with new weights and second - update feature with variation's values inside the rule (experiment). Executing 2 API calls is not atomic and may cause issues on client side who reads the data. I didn't find a way to update values of variations through update experiment API. Did I miss something? Or there another way of doing so?

Hi, when a variant has “won” in GrowthBook experiments, does Growthbook still collect data if the status of the test is “running”?