Analytics and Versioning

SDK analytics should answer product questions without making the donor path fragile. Add tracking after the widget renders correctly and the payment or registration path is tested.

Tracking

The SDK exposes track for supported events. Use it to connect Givebear embed activity with the surrounding website analytics strategy.

Track events that help staff understand behavior:

• Widget viewed.
• Donation flow opened.
• Donation button clicked.
• Calendar or event widget interacted with.
• Prayer-time widget viewed.

Do not send sensitive donor details into unrelated analytics tools unless the organization has a clear policy and user consent path.

Versioning mindset

The SDK is loaded from the Givebear app, so integrations should be written defensively:

• Load the script before calling methods.
• Check that window.Givebear exists.
• Keep configuration explicit.
• Avoid depending on undocumented internal DOM.
• Test key pages after dashboard, SDK, or website changes.

Release checklist

Before changing a live SDK integration:

1. Identify every page that loads the SDK.
2. Test the donor or attendee path.
3. Check browser console output.
4. Confirm mobile rendering.
5. Keep a rollback path, such as the previous embed snippet or direct public link.

If the integration only needs a static embed, prefer the widget guide. The SDK is best when code control is truly needed.