Estimate data requirements for Salesforce

[damiankay]

Detailed description of work: Before we launch Maker Party and Petitions Petition V2, the Salesforce team needs a data usage estimation. This would include:

1. A combination of the estimated numbers from the Foundation on Signers/Attendees etc.
2. Fission's estimation of daily API traffic to Salesforce.

Start date: September 7, 2016 Due date: September 16, 2016

CC: @shaghdoosti @valianttry @cadecairos @drewmoto

[damiankay]

@shaghdoosti do you know our how many signers we're projecting for the Petition, and how many event participants for Maker Party?

[shaghdoosti]

We're aiming for 100,000 petition signatures, and 300 events with about 40/50 attendees each.

On Wed, Sep 7, 2016 at 3:22 PM, Damian Kuehn notifications@github.com wrote:

@shaghdoosti https://github.com/shaghdoosti do you know our how many signers we're projecting for the Petition, and how many event participants for Maker Party?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MozillaFoundation/Advocacy/issues/331#issuecomment-245438303, or mute the thread https://github.com/notifications/unsubscribe-auth/AM_sEH4ofhKoqwz0WurGjw68OnfR4tk9ks5qnzkygaJpZM4J3ac6 .

Sara Haghdoosti Director, Advocacy Campaigns and Networks P: +16465494810 S: sara.haghdoosti

[damiankay]

Thanks @shaghdoosti

[damiankay]

From Fission: Based on the KPIs (100,000 petition signatures, and 300 events with about 40/50 attendees each) we can anticipate up to 300,000 API requests.

CC @drewmoto

[damiankay]

Lifecyle Marketing / Salesforce team actually needs estimated daily volume at launch and ongoing for campaigns and events. This means that we need to factor in not only Maker Party, but the Petition and any other integrations.

Our KPI for the Petition is 100K signatures. Are there any other integrations that I'm not aware of? @shaghdoosti @valianttry @vojtechmzl

CC @drewmoto @jendc123 @imagerwalt

[imagerwalt]

Hey @damiankay, not sure if I'm answering the questions, but the reason we have 300,000 API requests is due to the 100,000 petition signatures and each person has three api calls, 1) check if the user exists in order to prevent double entries, 2) insert or update user 3) add user to campaign.

The only other one that I'm aware of is the Maker Events. That will trigger three api calls per person, 1) check if user exists 2) insert/update user information with additional maker events info 3) add user to event.

On the code side they have entirely different structure, due to the NB having different standards for person signups and event creations, but for the SF API part, they are mostly the same.

[damiankay]

Thanks @imagerwalt . I think the issues is they need a daily estimate. It sounds like @vojtechmzl is probably the one to provide that. We'll multiply his number by 3 to get your estimated API calls.

Vojtech, can you please give us a daily estimate of Petition signers? And if possible, Maker Party hosts / RSVPs?

[vojtechsedlak]

Just a quick update, Andrew is aware of the expected traffic patterns in the next bit. Vojtech will keep him posted once dates are settled for forthcoming social, snippet and email launches.

[damiankay]

Thanks @vojtechmzl