============================
.. image:: https://circleci.com/gh/waveaccounting/vero-python.svg?style=svg
:target: https://circleci.com/gh/waveaccounting/vero-python
:alt: Circle CI
.. image:: https://readthedocs.org/projects/pip/badge/?version=latest
:target: https://vero.readthedocs.org/en/latest/
:alt: Read the Docs
Full documentation can be found on `ReadTheDocs <https://vero.readthedocs.org/en/latest/>`_
Vero is an API wrapper for event logging in your Python application.
Fetch your auth token from your `Vero <http://getvero.com>`_ account and use the python interface instead of `API <http://github.com/getvero/vero-api>`_ web hooks.
::
>>> from vero import VeroEventLogger
>>> logger = VeroEventLogger(auth_token)
>>> user_id = 42
>>> user_data = {
'full_name': 'Jane Doe'
}
>>> response = logger.add_user(user_id, user_data)
>>> response.status_code
200
Features
--------
Modify user data and log events. Run in live or test mode.
- Add user
- Delete user
- Edit user
- Add user tags
- Remove user tags
- Unsubscribe user
- Resubscribe user
- Add event
- Check heartbeat
Installation
------------
Install the package from PyPI
::
pip install vero
Run Tests
------------
Run Tests from command line.
::
VERO_AUTH_TOKEN=[ Your Token here ] python setup.py test
Usage
-----
Create instance
~~~~~~~~~~~~~~~
Use the authorization token from your Vero account page to create a VeroEventLogger object.
::
>>> from vero import VeroEventLogger
>>> auth_token = "foobar"
>>> logger = VeroEventLogger(auth_token)
After creating an instance of VeroEventLogger as ``logger`` use any of the following methods to access Vero.
Add user
~~~~~~~~
Create a new user with the information in ``user_data``. ``user_email`` is optional but is needed to trigger emails to the user.
::
>>> user_id = 1
>>> user_email = 'johndoe@example.com'
>>> user_data = {
'first name': 'John',
'last name': 'Doe'
}
>>> logger.add_user(user_id, user_data, user_email=user_email)
Edit user
~~~~~~~~~
Add or change fields in ``user_data`` for the user.
::
>>> user_id = 1
>>> user_data = {
'first name': 'Jane'
}
>>> logger.edit_user(user_id, user_data)
Add user tags
~~~~~~~~~~~~~
Add each tag in ``tag_list`` to the user.
::
>>> user_id = 1
>>> tag_list = ['blue', 'red', 'yellow']
>>> logger.add_tags(user_id, tag_list)
Remove user tags
~~~~~~~~~~~~~~~~
Remove each tag in ``tag_list`` from the user.
::
>>> user_id = 1
>>> tag_list = ['yellow']
>>> logger.remove_tags(user_id, tag_list)
Unsubscribe user
~~~~~~~~~~~~~~~~
Unsubscribe the user from triggering future events.
::
>>> user_id = 1
>>> logger.unsubscribe_user(user_id)
Resubscribe user
~~~~~~~~~~~~~~~~
Resubscribe the user to allow triggering future events.
::
>>> user_id = 1
>>> logger.resubscribe_user(user_id)
Add event
~~~~~~~~~
Note: adding an event with a user id that doesn't exist will create the user.
Event data can contain whatever fields are needed.
::
>>> user_id = 2
>>> user_email = 'janedoe@example.com'
>>> event_name = 'Visited Website'
>>> event_data = {
'date': 'today',
'visited': 'front page'
}
>>> logger.add_event(event_name, event_data, user_id, user_email=user_email)
Re-identify a user
~~~~~~~~~~~~~
Change a user's ``identifier`` (or ID) in Vero. This method accept their current (old) ``identifier`` and the ``identifier`` to replace it.
::
>>> user_id = 1
>>> new_user_id = 2
>>> logger.reidentify_user(user_id, new_user_id)
Delete user
~~~~~~~~~~~~~~~~
Delete the user
::
>>> user_id = 1
>>> logger.delete_user(user_id)
Metadata
Release files for vero 2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vero-2.0.1.tar.gz | 5.4 kB | Without provenance | Details for vero-2.0.1.tar.gz |
Release files / vero-2.0.1.tar.gz
| Download URL | vero-2.0.1.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccd0d1ea1b32adec383029de48927c989d8b770a33b78466b853bcfcbc1e5dc7
|
|
BLAKE2b-256 checksum How to use checksums |
45275dc555227de8a1e82fff614ce70787806891cd871f26783e62c6c2fdaa89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for vero 2.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.