RudderStack obtains event data from a source, which may be a tool or a network. The website, mobile app, and back-end server, to name a few, are all sources.
The term "destination" refers to a tool that receives your RudderStack event info. This data will then be employed by these destination tools for the activation use cases. Destinations include Google Analytics, Salesforce, and HubSpot, to call a couple of.
How to found out an occasion stream
Before you start, confirm you understand these terms utilized in this tutorial:
Source: RudderStack ingests the event data from a source, which can be a tool or a platform. Sources include the website, smartphone app, and back-end server, to call a couple of .
Destination: The term "destination" refers to a tool that receives your RudderStack event info. This data will then be employed by these destination tools for the activation use cases. Destinations include Google Analytics, Salesforce, and HubSpot, to call a couple of.
The steps for fixing an occasion stream in RudderStack open source are:
- Instrumenting an occasion stream source
- Configuring a warehouse destination
- Configuring a tool destination
- Sending events to verify the event stream
Step 1: Instrument an occasion stream source
To set up an occasion stream source in RudderStack:
Go to your RudderStack dashboard and log in. Please create a RudderStack account if you do not have one already. to line up your event streams, you'll use the RudderStack open source control plane.
The hosted control plane from RudderStack is often wont to handle your event stream configurations. It's very free, doesn't need any configuration, and features a few more features than the open-source control plane.
Assign a reputation to your source, and click on Next.
Step 2: Configure a warehouse destination
Important: Build a replacement project in your warehouse and a RudderStack user position with the acceptable permissions before configuring your data warehouse as a destination in RudderStack. The documents contain extensive, step-by-step directions for a way to try to do this together with your preferred warehouse.
This guide will show you ways to create a Google BigQuery warehouse destination. you do not need to find out a warehouse destination, but it's something I consider. The documentation explains the way to create a Google BigQuery project and a server account with the specified permissions.
Then, in RudderStack, set up BigQuery as a warehouse destination as follows:
Select Directory from the left navigation panel, then Google BigQuery from the drop-down menu:
Offer your destination credibility and then click Next.
Choose which source you would like to use to send the events to your destination. Select the source that you simply created within the previous section. Then, click on Next.
Specify the specified connection credentials. For this destination, enter the BigQuery Project ID and therefore the staging bucket name; information on the way to get this information is within the docs.
Copy the contents of the private JSON file you created, because the docs explain.
That concludes our discussion. In RudderStack, you've found your BigQuery warehouse as a target. RudderStack will automatically route events into your BigQuery and make your identity graph there until you begin submitting events from your source (in this case, a website).
Step 3: Configure a tool destination
Once you've added a source, follow these steps to configure a destination within the RudderStack dashboard:
To add a replacement destination, click on the Add Destination button
RudderStack supports over 80 destinations to which you'll send your event data. Choose your preferred destination platform from the list. This instance configures Google Analytics as a destination.
Add a reputation to your destination, and click on Next.
Next, choose the well-liked source. If you're following alongside this tutorial, choose the source you configured above.
In this step, you want to add the relevant Connection Settings. Enter the Tracking ID for this destination (Google Analytics). you'll also configure other optional settings per your requirements. Once you've added the specified settings, click Next.
Step 4: Send test events to verify the event stream
The rudder-server repo includes a shell script that generates test events. Get the source Write Key from step 2, and run the subsequent command:
To check if the test events are delivered, attend your Google Analytics dashboard, navigate to Realtime under Reports, and click on Events.