We'll send you updates from the blog and monthly release notes.
November 4, 2021
The first impression that any company has on potential customers is page speed, which has a significant impact on user experience. Immediately after that first impression, website performance issues take center stage in forming customers’ opinions including time to render, time to interact, DNS lookup speed, memory usage, and more. In the past, engineers have faced the difficult choice of prioritizing page performance above everything else or implementing tools on their site to help with business needs. The lack of tooling and development kits around SDK performance is a big contributor to this pain point.
Performance is increased, but the icing on the case is that the SDK still routes this data in real time to tools like Snowflake, Amazon S3, Salesforce, Slack, Google Analytics, Customer.io, and more. With this data, all of our core business functions, from sales and marketing to recruiting and customer support, are able to access the data they need in order to better serve our customers and growing business.
We also allow developers to filter selective destinations to send event data. You can send your event data only to a few intended destinations by filtering out the rest. You can do so by passing an integrations object in the options parameter of the identify(), page(), and track() methods. We support over 150 destinations from Salesforce and Slack to Redshift and BigQuery.
Best of all, we offer a Live Viewer that makes troubleshooting events a straightforward process.
Context and Traits in RudderStack
RudderStack gives developers the option to automatically capture certain event-specific and user-specific data, based on the type of the event (see the following examples). The context and trait dictionaries can be included within the options argument which is included in the identify(), page(), and track() methods. A context is a dictionary of additional information about a particular data, such as a user’s IP address. A trait is an optional dictionary included within context, which specifies the unique traits of the user. This is a very useful field for linking information of a user from a previously made identify() call to a track() or page() event.
RudderStack's Querystring API allows you to trigger track and identify calls using the query parameters. For example, the ajs_uid parameter makes a rudderanalytics.identify() call with userId having the parameter value (see our docs and FAQ for more information).
Detecting Ad-blocked Pages
Customer and Partner Marketing