Python
Detailed technical documentation on using RudderStack’s Python SDK to send events to various destinations
RudderStack’s Python SDK allows you to track your customer event data from your Python code. Once enabled, the event requests hit the RudderStack servers. RudderStack then routes the events to the specified destination platforms as configured by you.
Find this SDK in our GitHub repository.
Installing the RudderStack Python SDK
To install the RudderStack Python SDK using pip, run the following command:
pip install rudder-sdk-python
Initializing the RudderStack Client
To initialize the RudderStack client, run the following code snippet:
import rudder_analytics
rudder_analytics.write_key = WRITE_KEYrudder_analytics.data_plane_url = DATA_PLANE_URL
For more information on how to get the source write key, refer to this section.
For more information on how to get your data plane URL, refer to this section.
Sending Events from RudderStack
Once the RudderStack client is initialized, you can use it to send relevant customer events from the RudderStack client.
A sample track
call is as shown :
rudder_analytics.track('developer_user_id', 'Simple Track Event', { 'key1': 'val1'})
Identify
The identify
call lets you identify a visiting user and associate them to their actions.
For more information on the identify
call, refer to the RudderStack API Specification guide.
An example identify
call is as shown:
rudder_analytics.identify('123456', { 'email': 'name@surname.com', 'name': 'John Doe', 'friends': 16})
The identify
method parameters are as described below:
Field | Type | Presence | Description |
---|---|---|---|
anonymousId | String | Optional | Sets the user ID for cases where there is no unique identifier for the user. Either userId or anonymousId is required. |
userId | String | Optional, if anonymousId is already set | Unique identifier for a particular user in your database. |
context | Object | Optional | Dictionary of information that provides context about a message. However, it is not directly related to the API call. |
integrations | Object | Optional | A dictionary containing the destinations to be either enabled or disabled. |
timestamp | Date | Optional | The timestamp of the message's arrival. |
traits | Object | Optional | Dictionary of the traits associated with the user, such as name or email |
Track
The track
call lets you record the customer events, i.e. the actions that they perform, along with any properties associated with them.
For more information on the track
call, refer to the RudderStack API Specification guide.
An example track
call is as shown:
rudder_analytics.track('123456', 'Article Read', { 'title': 'The Independence', 'subtitle': 'Story of the Weak', 'author': 'John Doe'})
The track
method parameters are as described below:
Name | Type | Presence | Description |
---|---|---|---|
user_id | String | Required | The developer identification for your user |
event | String | Required | Name of the event being performed by the user |
properties | Object | Optional | Dictionary of the properties associated with a particular event. |
context | Object | Optional | Dictionary of information that provides context about a message. However, it is not directly related to the API call. |
timestamp | Date | Optional | The timestamp of the message's arrival. |
anonymous_id | String | Optional | Sets the user ID for cases where there is no unique identifier for the user. Either userId or anonymousId is required. |
integrations | Object | Optional | A dictionary containing the destinations to be either enabled or disabled. |
Page
The page
call lets you record your page views with any additional relevant information about the viewed page.
For more information on the page
call, refer to the RudderStack API Specification guide.
An example page
call is as shown:
rudder_analytics.page('userid', 'Documentation', 'Sample Doc', { 'url': 'http://rudderstack.com'})
The page
method parameters are as described below:
Field | Type | Presence | Description |
---|---|---|---|
anonymousId | String | Optional | Sets the user ID for cases where there is no unique identifier for the user. Either userId or anonymousId is required. |
userId | String | Optional, if anonymousId is already set | Unique identifier for a particular user in your database. |
context | Object | Optional | Dictionary of information that provides context about a message. However, it is not directly related to the API call. |
integrations | Object | Optional | A dictionary containing the destinations to be either enabled or disabled. |
name | String | Required | Name of the page being viewed. |
properties | Object | Optional | Dictionary of the properties associated with the page being viewed, such as url and referrer |
timestamp | Date | Optional | The timestamp of the message's arrival. |
Screen
The screen
call lets you record whenever your user views their mobile screen with any additional relevant information about the screen.
For more information on the screen
call, refer to the RudderStack API Specification guide.
An example screen
call is as shown:
rudder_analytics.screen('userid', 'Settings', 'Brightness', { 'from': 'Settings Screen'})
The screen
method parameters are as described below:
Field | Type | Presence | Description |
---|---|---|---|
anonymousId | String | Optional | Sets the user ID for cases where there is no unique identifier for the user. Either userId or anonymousId is required. |
userId | String | Optional, if anonymousId is already set | Unique identifier for a particular user in your database. |
context | Object | Optional | Dictionary of information that provides context about a message. However, it is not directly related to the API call. |
integrations | Object | Optional | A dictionary containing the destinations to be either enabled or disabled. |
name | String | Required | Name of the screen being viewed. |
properties | Object | Optional | Dictionary of the properties associated with the page being viewed, such as url and referrer |
timestamp | Date | Optional | The timestamp of the message's arrival. |
Group
The group
call allows you to link an identified user with a group, such as a company, organization, or an account. It also lets you record any custom traits associated with that group, such as the name of the company, the number of employees, etc.
For more information on the group
call, refer to the RudderStack API Specification guide.
An example group
call is as shown:
rudder_analytics.group('userid', 'groupid', { 'name': 'Company', 'domain': 'IT'})
The group
method parameters are as follows:
Field | Type | Presence | Description |
---|---|---|---|
anonymousId | String | Optional | Sets the user ID for cases where there is no unique identifier for the user. Either userId or anonymousId is required. |
userId | String | Optional, if anonymousId is already set | Unique identifier for a particular user in your database. |
context | Object | Optional | Dictionary of information that provides context about a message. However, it is not directly related to the API call. |
integrations | Object | Optional | A dictionary containing the destinations to be either enabled or disabled. |
groupId | String | Required | Unique identifier of the group, as present in your database. |
traits | Object | Optional | Dictionary of the properties or traits associated with the group, such as email or name . |
timestamp | Date | Optional | The timestamp of the message's arrival. |
Alias
The alias
call lets you merge different identities of a known user.
alias
is an advanced method. However, it is required when managing user identities in some destinations.The following downstream destinations support the alias
call:
- [**MoEngage**](https://rudderstack.com/docs/destinations/marketing/moengage/)
- [**Kissmetrics**](https://rudderstack.com/docs/destinations/analytics/kissmetrics/)
- [**Amplitude**](https://rudderstack.com/docs/destinations/analytics/amplitude/) \(only supported by the [**JavaScript SDK**](rudderstack-javascript-sdk/) via [**Cloud Mode**](https://rudderstack.com/docs/connections/rudderstack-connection-modes/#cloud-mode)\)
For more information on the alias
call, refer to the RudderStack Events Specification guide.
An example alias
call is as shown:
rudder_analytics.alias('previousid', 'userid')
The alias
method parameters are as mentioned below:
Field | Type | Presence | Description |
---|---|---|---|
userId | String | Optional, if anonymousId is already set | Unique identifier for a particular user in your database. |
context | Object | Optional | Dictionary of information that provides context about a message. However, it is not directly related to the API call. |
integrations | Object | Optional | A dictionary containing the destinations to be either enabled or disabled. |
previousId | String | Required | The previous unique identifier of the user. |
traits | Object | Optional | Dictionary of the properties or traits associated with the group, such as email or name . |
timestamp | Date | Optional | The timestamp of the message's arrival. |
For more information on the alias
call, refer to the RudderStack API Specification guide.
Error Handling
To handle errors that may occur when sending these events via rudder_analytics
you can declare a callback called on_error
.
def on_error(error, events): print("Error response:", error)
rudder_analytics.on_error = on_error
NOTE: this will only return errors that may occur with the HTTP request to the Gateway. Any errors that occur downstream will not be returned via this callback.
Common request responses from the Gateway are as follows
Status | Code |
---|---|
Ok | 200 |
Request neither has anonymousId nor userId | 400 |
Invalid Write Key | 401 |
Invalid JSON | 400 |
Contact Us
To know more about the RudderStack Python SDK, you can contact us. You can also start a conversation on our Slack channel; we will be happy to talk to you.