Frequently asked questions

Splunk University will be held at The Venetian Las Vegas from July 15-17 and July 20, 2023. More information about the event will be announced in the coming months.

Sign up now to get the latest notifications from Splunk about .conf events.

At .conf23, you’ll learn how Splunk can help you make your organization more resilient. And have some fun while you’re at it.

What does that really mean?

• Get inspired by experts and dive into industry trends. 
• Roll up your sleeves and experiment with Splunk products during interactive learning sessions. 
• Share your unique Splunk product challenges and get help solving them from Splunk pros and our enthusiastic community of practitioners. 
• Network with fellow Splunk fans to discuss use cases, be they mission-critical (like preventing security threats) or more for fun (Beer brewing! Beekeeping!). 
• Discover all the services available to you as a Splunk user or customer. 
• Catch up with other builders and developers to discover how they’re solving their most critical business problems using Splunk products. 
• See Splunk technology in action during breakout sessions or in the source=*Pavilion. 
• Check in with Splunk partners who are providing complex integrations. 
• Attend post-session parties, compete in capture-the-flag-esque competitions, maybe even bust out some dance moves.
  

We could go on. But we think being there in person will answer this question best.

Registration opens in the spring. Come back in late March for registration details!

If you’d like to take advantage of the conference discount, we recommend waiting to book your hotel until official registration opens in March. 

Yes, you can watch .conf content on demand.

.conf Online features breakouts from .conf20, .conf21 and .conf22 — to access, sign-up or log-in with a splunk.com account.

Please reach out to our sponsorship team at confsponsors@splunk.com for more information.

Please email confteam@splunk.com and we’ll be happy to help.

The Call for Speakers (CFS) process for .conf23 opens Jan 25, 2023 and closes Mar 2, 2023. Abstracts received after Mar 2 at 11:59 pm PT will not be considered. 

• All titles and abstracts must be written in English, and accepted sessions presented in English. 
  
• Submission details can only be submitted online via the Call for Speakers submission portal; fax, post or email submissions will not be considered. 
  
• Titles have a max character count of 150 characters, and abstracts should be no more than 500 characters and should include a high-level overview of what you hope to accomplish in the session. Be sure to check out our CFS resources on the Call for Speakers page.
  
• Once submitted in the tool, you will be able to make updates to your submission up until Mar 2 @ 11:59 pm PT, when CFS closes.  
  

You bet! Check out the Call for Speakers page for more resources. Here are some other key things to keep in mind while writing your proposal. 

• Avoid starting your session description with the phrase, "In this session, we will ..." or "In this session, you will learn ..." Instead, try a rhetorical question, or an interesting industry data point to start your session abstract. 
  
• Make sure that what you submit will be what you present. Nothing upsets attendees more than signing up for a session that was not as advertised.
  
• Your abstract should generate enthusiasm, so make sure your content is both relevant and exciting. What invaluable information will you share during the session?
  
• Use the tags in the system thoughtfully for topics, levels and roles. Who is the target audience? What products or topics does this session cover outside of the track name? What roles would benefit from participating in this session?
  
• Take time to draft well-written titles, abstracts, and learning objectives for your submission. A thoughtful submission has a better chance of being selected and, if accepted, will be seen by thousands of attendees once published in the session catalog.
  
• When introducing abbreviations or acronyms, spell out the full name or title, followed by the abbreviation or acronym in parentheses. You can then use the abbreviation or acronym by itself. Don't assume your audience knows what an abbreviation or acronym stands for. Example: Internet of Things (IoT)
  
• Avoid all caps (unless the official spelling denotes the use of all caps), exclamation points and other casual/personal styles of writing in the proposed title or abstract.
  
• Have someone outside of your field of work proofread your title and abstract before submission. While the person may not understand the technical terms or references, they can help catch grammatical/spelling errors and determine if you are communicating the goals of your submission effectively.
  
• Make sure your submission doesn't sound like a sales pitch, but rather an exciting opportunity for attendees to learn something new. Breakout sessions are intended to be educational and are the number one reason attendees come to .conf each year.
  
• Check out the session type descriptions on our Sessions page. There, you’ll find more info about session formats, including our new interactive workshops.
  

• Don't use abbreviations or acronyms in the titles of your submissions.
  
• Don't use competitor or other company names in your submission titles. If you're highlighting other companies within your session, you can include these names within the description.
  
• Use clear and concise language that attendees will immediately understand. The agenda will be packed, and attendees need to easily identify sessions they’re interested in.
  
• Straightforward language like "introduction to," "deep dive" and "case study" are popular examples because they quickly give the attendee important information about the session.
  

Sure, we welcome multiple submissions. Please keep in mind, though, that we favor quality over quantity — simply submitting multiple session proposals will not increase your chances of having a session selected.

Sessions will be selected based on the content as well as the proposed speaker(s). If a speaker has presented at a .conf event or Splunk event in the past, the Review Committee will look at speaker scores and session popularity and take them into consideration during the selection process.

Unfortunately, we can’t give individual feedback if your proposal is declined. However, these are the main reasons why a session may not make it into .conf23:

• The submission doesn’t contain content included in the themes and topics outlined by Splunk for .conf23. Explore themes on our Call for Speakers page.
• The session topic isn't unique or overlaps with another more appropriate abstract.
  
• The title or abstract isn’t clearly written — ideas are ambiguous, goals aren’t established and there are grammatical/spelling errors.
  
• The content isn't relevant to the indicated audience.
  
• The session value isn't clearly identified.
  

1. You should receive a confirmation email that your proposal has been submitted.
   
2. All co-presenters will receive an email asking them to confirm their presenter details.
   
3. A committee of subject-matter experts, including Splunk team members, conduct a comprehensive review process of all the submitted abstracts.
   
4. You’ll receive an update late March about the status of your submission from confspeakers@splunk.com. If your submission is accepted, a Planning Manager will reach out to you to schedule some time on your calendar to kick things off. 
   

Please email confspeakers@splunk.com and we’ll get you sorted.