7
7
documentation`_. If your users are interacting with your application via the
8
8
web, you may also be interested in our `JavaScript library`_.
9
9
10
- .. _`Javascript library`: https://developer.mixpanel.com/docs/javascript
10
+ .. _`JavaScript library`: https://developer.mixpanel.com/docs/javascript
11
11
.. _`usage documentation`: https://developer.mixpanel.com/docs/python
12
12
13
13
:class:`~.Mixpanel` is the primary class for tracking events and sending People
@@ -115,7 +115,8 @@ def import_data(self, api_key, distinct_id, event_name, timestamp,
115
115
:param dict meta: overrides Mixpanel special properties
116
116
:param str api_secret: Your Mixpanel project's API secret.
117
117
118
- Important: Mixpanel's ``import`` HTTP endpoint requires the project API
118
+ .. Important::
119
+ Mixpanel's ``import`` HTTP endpoint requires the project API
119
120
secret found in your Mixpanel project's settings. The older API key is
120
121
no longer accessible in the Mixpanel UI, but will continue to work.
121
122
The api_key parameter will be removed in an upcoming release of
@@ -128,7 +129,7 @@ def import_data(self, api_key, distinct_id, event_name, timestamp,
128
129
``track`` endpoint disallows events that occurred too long ago. This
129
130
method can be used to import such events. See our online documentation
130
131
for `more details
131
- <https://developer.mixpanel.com/docs/importing-old -events>`__.
132
+ <https://developer.mixpanel.com/reference/events#import -events>`__.
132
133
"""
133
134
134
135
if api_secret is None :
@@ -165,7 +166,7 @@ def alias(self, alias_id, original, meta=None):
165
166
Events triggered by the new id will be associated with the existing
166
167
user's profile and behavior. See our online documentation for `more
167
168
details
168
- <https://developer.mixpanel.com/docs/http#section -create-alias>`__.
169
+ <https://developer.mixpanel.com/reference/identities#identity -create-alias>`__.
169
170
170
171
.. note::
171
172
Calling this method *always* results in a synchronous HTTP request
@@ -194,7 +195,8 @@ def merge(self, api_key, distinct_id1, distinct_id2, meta=None, api_secret=None)
194
195
:param dict meta: overrides Mixpanel special properties
195
196
:param str api_secret: Your Mixpanel project's API secret.
196
197
197
- Important: Mixpanel's ``merge`` HTTP endpoint requires the project API
198
+ .. Important::
199
+ Mixpanel's ``merge`` HTTP endpoint requires the project API
198
200
secret found in your Mixpanel project's settings. The older API key is
199
201
no longer accessible in the Mixpanel UI, but will continue to work.
200
202
The api_key parameter will be removed in an upcoming release of
@@ -205,7 +207,7 @@ def merge(self, api_key, distinct_id1, distinct_id2, meta=None, api_secret=None)
205
207
206
208
See our online documentation for `more
207
209
details
208
- <https://developer.mixpanel.com/docs/http# merge>`__.
210
+ <https://developer.mixpanel.com/reference/identities#identity- merge>`__.
209
211
"""
210
212
if api_secret is None :
211
213
logger .warning ("api_key will soon be removed from mixpanel-python; please use api_secret instead." )
@@ -372,12 +374,12 @@ def people_update(self, message, meta=None):
372
374
373
375
:param dict message: the message to send
374
376
375
- Callers are responsible for formatting the update message as documented
376
- in the `Mixpanel HTTP specification `_. This method may be useful if you
377
+ Callers are responsible for formatting the update message as described
378
+ in the `user profiles documentation `_. This method may be useful if you
377
379
want to use very new or experimental features of people analytics, but
378
380
please use the other ``people_*`` methods where possible.
379
381
380
- .. _`Mixpanel HTTP specification `: https://developer.mixpanel.com/docs/http
382
+ .. _`user profiles documentation `: https://developer.mixpanel.com/reference/user-profiles
381
383
"""
382
384
record = {
383
385
'$token' : self ._token ,
@@ -489,11 +491,11 @@ def group_update(self, message, meta=None):
489
491
:param dict message: the message to send
490
492
491
493
Callers are responsible for formatting the update message as documented
492
- in the `Mixpanel HTTP specification `_. This method may be useful if you
494
+ in the `group profiles documentation `_. This method may be useful if you
493
495
want to use very new or experimental features, but
494
496
please use the other ``group_*`` methods where possible.
495
497
496
- .. _`Mixpanel HTTP specification `: https://developer.mixpanel.com/docs/http
498
+ .. _`group profiles documentation `: https://developer.mixpanel.com/reference/group-profiles
497
499
"""
498
500
record = {
499
501
'$token' : self ._token ,
0 commit comments